-
Notifications
You must be signed in to change notification settings - Fork 104
Memory Leak - observed on Apollo3 / Artemis #135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Starting a diagnosis with v2.2.8 of this library: have we got a memory leak - depending on how the This code should run forever, and it seems to (on Apollo3 v2.2.1):
Here are the first 600 cycles. The blue line is the success count; the red line is the fail count (zero): Leave it running for a while; all is well: |
Change the code, creating and re-using
and it goes BOOM after a 1323 cycles ("out of memory"): |
OK. What to add...? I did write an Change the loop to:
and it still goes boom after 1334 cycles: Time for some head-scratching... Watch this space! |
Is this specific to the Apollo3? What do we see on the SparkFun RedBoard ATmega328P with its tiny amount of RAM? The ATmega328P does not support
I see three successful begins, then it's all fails...: OK. That's different. But at least the code keeps on running... Any clues in the debug messages? Ah, yes, there we go... Out of memory on |
OK. Time to add that destructor!
Ta da! That does the trick! (On ATmega328P): |
Where are we on Apollo3? Ah, the sweet smell of success!! Apologies @ricozinn for all the head-scratching caused. And thanks again for reporting. v2.2.9 will go live shortly. Best wishes, |
v2.2.9 - add a destructor to resolve issue #135
Hah, you thank me for reporting a bug but I thought I did a terrible job reporting on the issue (and I really did). Thanks for doing all the work! Mine was specifically a "stack overflow" error though and I only saw it when I also included the ArduinoBLE library and was connected to a central. Anyway, I'll try out the release when it comes out. Thanks again! |
Based on this forum issue:
Richard (@ricozinn) is observing what looks like a memory leak on Apollo3 (Artemis) v2.2.1
The text was updated successfully, but these errors were encountered: