Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Opening a websocket connection inevitably leads to a "Run-Time Check Failure #2" #11

Open
mamome4 opened this issue May 2, 2022 · 0 comments
Open

Opening a websocket connection inevitably leads to a "Run-Time Check Failure #2" #11

mamome4 opened this issue May 2, 2022 · 0 comments
Assignees
@BennyGK15 @mamome4 @masasume
Labels
bug Something isn't working

Comments

@mamome4
Copy link
Collaborator

mamome4 commented May 2, 2022

Opening a websocket connection inevitably leads to a "Run-Time Check Failure #2- Stack around the variable 'key' was corrupted".
This happens after line 2492 "return ERR_OK; /* We handled this */"
@mamome4 mamome4 added the bug Something isn't working label May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BennyGK15 BennyGK15

@mamome4 mamome4

@masasume masasume

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@BennyGK15 @mamome4 @masasume