-
-
Notifications
You must be signed in to change notification settings - Fork 269
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
Data race on Conn.closeErr
#436
Milestone
Comments
I realise there is a PR #427 for it. |
nhooyr
added a commit
to alixander/websocket
that referenced
this issue
Apr 5, 2024
Far simpler now. Sorry this took a while. Closes nhooyr#427 Closes nhooyr#429 Closes nhooyr#434 Closes nhooyr#436 Closes nhooyr#437
Thanks for reporting. I've fixed this in #427. Please review and let me know if you see anything else. |
nhooyr
added a commit
to alixander/websocket
that referenced
this issue
Apr 5, 2024
Far simpler now. Sorry this took a while. Closes nhooyr#427 Closes nhooyr#429 Closes nhooyr#434 Closes nhooyr#436 Closes nhooyr#437
Sorry for the delay. Fixed by #427. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I run my go program with race detector enabled, following logs were observed.
Apparently it's because when it's being set, it's protected by
c.closeMu
.websocket/close.go
Line 288 in e3a2d32
However it's not when it's being read.
websocket/close.go
Line 117 in e3a2d32
The text was updated successfully, but these errors were encountered: