Skip to content

Fix large memory leak in ScheduledThreadPoolExecutor handling - #177

Merged
jeremyestein merged 1 commit into
jeremy/make-grafana-viewablefrom
jeremy/mem-leak
Sep 11, 2026
Merged

jeremyestein merged 1 commit into
jeremy/make-grafana-viewablefrom
jeremy/mem-leak

Conversation

@jeremyestein

Copy link
Copy Markdown
Collaborator

Was causing an ever-increasing number of ScheduledThreadPoolExecutor$ScheduledFutureTask objects (and other related objects) to be retained.

It was treating a ThreadPoolTaskScheduler as a poller, which seems to have caused 10s of millions of these objects to accumulate (corresponds approx to the 1 object per 10ms polling interval for the 7 days it had been running).

@jeremyestein
jeremyestein marked this pull request as ready for review September 10, 2026 13:20

@skeating skeating left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch

@jeremyestein
jeremyestein added this pull request to stack #182 September 10, 2026 16:51
ScheduledThreadPoolExecutor$ScheduledFutureTask objects (and other
related objects) to be retained.
@jeremyestein
jeremyestein merged commit 55a35be into develop Sep 11, 2026
7 checks passed
@jeremyestein
jeremyestein deleted the jeremy/mem-leak branch September 11, 2026 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants