Skip to content

auto-pause: make it memory-leak proof #10596

@medyagh

Description

@medyagh

each call of time.After creates a new timer instance which is not released until the timer fired. If we have high traffic in incomeCh we'll end up with a lot of pending timers

https://groups.google.com/g/golang-nuts/c/cCdm0Ixwi9A

Originally posted by @ilya-zuyev in #10427 (comment)

https://www.fatalerrors.org/a/use-with-caution-time.after-can-cause-memory-leak-golang.html

Metadata

Metadata

Labels

co/auto-pausekind/featureCategorizes issue or PR as related to a new feature.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions