-
-
Notifications
You must be signed in to change notification settings - Fork 512
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
Stack canary watchpoint triggered (async_tcp) when accessing Web UI #2316
Comments
Log 2 (notice the PS register is slightly different, so yes, this is actually a second instance of the panic 😉)
Have to put this in a new comment, as otherwise the first comment (issue report) is longer than |
@schlimmchen yes the expected behaviour is a kind of silly question in case of a race condition or common bug. But we introduced this as part of the original github issue template, form follows function here. What astonished me is the frequent occurrence of AuthenticationMiddleware, but then I havent peeked at a stack trace often, recently. Is this part of some SSL stack I am unaware of or is this the safety check for the AdminPassword for most of the requests ? |
Yes. My best guess is that something (ESPAsyncWebServer) iterates this middleware chain, but the chain is corrupted, such that the loop does not stop where it is supposed to. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns. |
What happened?
I am seeing this quite often recently. So often that I now think it is a third kind of new panic. And now that it happened in the upstream project as well, at least twice, I am leaving this here...
To Reproduce Bug
As the backtraces show, this type of panic occurs when accessing the web interface, but it is not perfectly reproducible.
Expected Behavior
(This field is stupid when reporting a panic 😁)
Install Method
Pre-Compiled binary from GitHub releases
What git-hash/version of OpenDTU?
b206cee
What firmware variant (PIO Environment) are you using?
generic_esp32s3_usb
Relevant log/trace output
No response
Anything else?
Log 1
Notes
Please confirm the following
The text was updated successfully, but these errors were encountered: