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.

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

fix connection close race #342

Merged
merged 1 commit into from
Mar 8, 2020
Merged

fix connection close race #342

merged 1 commit into from
Mar 8, 2020

Conversation

eikenb
Copy link
Member

@eikenb eikenb commented Mar 7, 2020

Need to prevent Close from being called at the same time. The lock
already existed, but was only used in one place where it should be
applied generally.

Fixes #333

Need to prevent Close from being called at the same time. The lock
already existed, but was only used in one place where it should be
applied generally.
@eikenb
Copy link
Member Author

eikenb commented Mar 7, 2020

Threw this up as a pull request in case anyone could come up with a test case. I know of no good way to reproduce data races in general so skipped it.

@eikenb eikenb added the bug label Mar 7, 2020
@eikenb eikenb added this to the v1.11.1 milestone Mar 7, 2020
@eikenb eikenb merged commit 0e12323 into master Mar 8, 2020
@eikenb eikenb deleted the issue-333-conn-close-race branch March 8, 2020 22:08
@eikenb eikenb modified the milestones: v1.11.1, v1.12.0 Jul 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

data race when deferring a Close()
2 participants