-
Notifications
You must be signed in to change notification settings - Fork 183
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
websocket demo issue #43
Comments
Hello, Thanks for the bug report. Indeed the websocket example doesn't work for me too in Concerning the string handling issue, can you be more specific? I've retested the example using valgrind and nothing popped for valgrind, the memory was clean. If you confirm this memory problem, can you open a new issue in github? Thanks for your help! |
Hello again, I think I solved the problem on the websocket_example. Can you check the branch fix-websockets and tell me if the problem is fixed on your side? It's not complete yet because I've seen I'm not fully RFC compliant but this will be addressed soon. |
I checked out the branch but on my side it's worth. |
did you update |
I had not the first time. |
When you open the browser console (F12), what does the error say? |
For firefox: WebSocket |
What does the connection says in the network tab? |
*** Error im './websocket_example': double free or corruption (fasttop): 0x75300cf8 *** |
I've pushed some more in the Can you re-run your tests with this new code? |
Thanks that works now for both Chrome and Firefox. |
Could you please let me know when you will merge this corrective branch into the master? |
That's an excellent news! |
Hi,
I am interested in the websocket demo. The demo works with Firefox but it doesn't work with Chrome.
When the websocket connection request is sent, the websocket is created and then directly deleted.
Also, there is an issue with string handling.
Please let me know if I can support you.
Best regards,
Michael
The text was updated successfully, but these errors were encountered: