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

Potential goroutine leak introduced by time.After #41

Closed
jerrypnz opened this issue Feb 6, 2017 · 1 comment
Closed

Potential goroutine leak introduced by time.After #41

jerrypnz opened this issue Feb 6, 2017 · 1 comment

Comments

@jerrypnz
Copy link

jerrypnz commented Feb 6, 2017

Recently we found a bug in our code where the usage of time.After in a tight receive loop caused OOM. I see a similar pattern in consume.go and thought it may be an issue here as well.
@fgeller
Copy link
Owner

fgeller commented Feb 6, 2017

cf doc in https://golang.org/src/time/sleep.go#L131

@fgeller fgeller closed this as completed in 6246d49 Feb 6, 2017
rogpeppe pushed a commit to rogpeppe-contrib/kt that referenced this issue Mar 23, 2022
@sixstone-qq
Merge pull request fgeller#41 from heetch/update-deps
8a5f05b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fgeller @jerrypnz