-
Notifications
You must be signed in to change notification settings - Fork 13.3k
eraseConfig() causes crashes #6063
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
Please decode the stack dump. Those hex numbers are useless without the decoded info as we don't have your exact binary to reverse them against. That said, I was able to repro the failure on GIT head, occasionally. Most times I could get 3 loops then crash, but one time it just ram forever (or at least the 10 mins and 600 loops or so before I tried something else). When the When I did the stack trace it was somewhere in the SDK ROM calling an alloc or free (seemed to vary), but there was memory corruption so the UMM memory manager crashed. Adding IRQ disables around all our own calls into the SDK had no effect. Crashes occurring in ROM code on memory callbacks, always.
|
And I think the getFreeHeap() stuff is just an artifact of the memory corruption and not something alloc'ing 30KB... |
|
Ok, here is the second.
|
Those traces should now be proper. |
Thanks, @adrionics . It's the same as the others, though, memory corruption causing either UMM crashes or OOM because the heap is in an inconsistent state. Not sure the best way to track it down, but as the two calls in question are very thin wrappers around SDK functions you might want to start talking on the espressif BBS and nonos-sdk sites and see if they're known... |
I posted on expressif BBS. We will see if they respond. |
Platform
Settings in IDE
Problem Description
After working on an issue related to #2186 (comment), I added an eraseConfig() into my code. After doing that, I started to see some weird behavior. One instance, the ESP will crash. This post is a result of working on understanding why it crashes and the very simple MCVE produces crashes in various ways. Any insight as to why is welcomed.
MCVE Sketch
Debug Messages
Notice the getFreeHeap values in the last lines.
The text was updated successfully, but these errors were encountered: