-
Notifications
You must be signed in to change notification settings - Fork 638
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
Crash when refreshing embedded website multiple times #1824
Comments
Does look like basic OOM, since we are running sensor image and trying to send large json blob while first ws client is still connected. I have not tested WebUI much since then, sorry. Whole communications process needs reworking, including ws server module. Also, using older Core with 12KB less available heap redoubles the issue I already referenced this issue in #1823 , since it does look like the same issue. Also, #1731 |
If I can help, let me know because this is very annoying for me, maybe using CSV to reduce the data blob as a hotfix? not sure how to start with this. |
Ordering somewhat complicates things. We need to wait up until the first connection finishes to send anything. Maybe even restore the old behaviour that sends configuration in chunks, implementing a proper queueing of outgoing data (because we hit network buffer limits / ws queue limits and lose it if not careful). ESPAsyncWebServer was updated recently with queue size check methods, so i hope it will help to avoid any subclassing / reworking of the ws handler there. |
perfect, then I have time to understand this project to try to fix it in the future if needed it. |
Just a note about the process + ref #1589 |
Closing via #1843 |
Bug description
While preparing the Shelly 1PM PR support When open espurna website and refresh multiple times it crashes and restarts the device, it's an error in this line:
espurna/code/espurna/ws.ino
Line 389 in 746ad70
Steps to reproduce
Device information
It has enabled
HJL01 / BL0937
andNTC
support, these variables could create a JSON parse error.Tools used
Additional context
Stack trace
Encoded stack trace
The text was updated successfully, but these errors were encountered: