-
-
Notifications
You must be signed in to change notification settings - Fork 350
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 in chat example #782
Comments
I missed the fact that #686 was closed, so I'll just add that I get the same thing after updating from 1.0+5 to 1.1.0 (and in master).
|
And, when running a single POST under valgrind:
|
When accessing the In the first terminal window:
In the second terminal window:
In the third terminal window:
Log output:
#782 (comment) : Because the webpage automatically accesses the /logs/ endpoint upon opening, the same error occurs. It might be an issue with resource management? 😢 I tried to debug but couldn't pinpoint the root cause. My environment information:
|
Suddenly ran into the same problem. A very ugly crash can be avoided by adding The library seems ingenious, but the first run of the example pushed back hard. |
When running example_chat and sending any input via the served example_chat.html page, the server crashes:
Backtrace:
This may be the same as #686. But just guessing as the reporter did not provide further info.
My build configuration:
I can attach the Valgrind output if needed. It is a bit hard to decipher but points to an issue with the memory management of connection objects.
The text was updated successfully, but these errors were encountered: