-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Potential memory corruption in stream_line_reader
#2028
Comments
Hmm no sorry it still does not resolve the problem |
Btw, it can only be triggered with a large payload, and it does not work 100% of the time.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I would like to report a recent problem that I found on the latest version 0.18.5
To test it, I compiled this simple program:
Upon running it, I place a breakpoint when calling
parse_request_line
The buffer of
stream_line_reader
seems to contains data from somewhere else:Please note that, this happens 80% of the time. When it work correctly, the buffer must contains HTTP request data:
When the server first started, the first request never has this problem. This suggest that there maybe race condition between threads when accessing a shared variable.
The text was updated successfully, but these errors were encountered: