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

time: time.After uses memory until duration times out #15698

ston1th opened this issue May 16, 2016 · 2 comments


None yet
4 participants
Copy link

commented May 16, 2016

I would like to see some memory usage information in the docs for time.After like time.Tick already has.


This comment has been minimized.

Copy link

commented May 16, 2016

See also: #8895 and #8898

But worst case we can just document something.

@bradfitz bradfitz added this to the Go1.8 milestone May 16, 2016


This comment has been minimized.

Copy link

commented May 19, 2016

I just got bit by this; after 10 minutes of execution, my program had 80MB used just by timers.

For now I've switched to NewTimer so I can explicitly stop them.

Looking forward to the fix.

@gopherbot gopherbot closed this in 7ab698b May 20, 2016

@golang golang locked and limited conversation to collaborators May 20, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.