Repository navigation
Memory leak: Uncleaned timeouts, intervals, and subscriptions #9156
Description
Problem
Several small memory leaks exist across the codebase from uncleaned timeouts, intervals, and event subscriptions:
WebFetch Timeout (webfetch.ts)
When fetch throws an error, the timeout is not cleared:
const timeout = setTimeout(...)
try {
const response = await fetch(...)
} catch (error) {
// timeout still running!
throw error
}Models setInterval (models.ts)
A setInterval is created for model refresh but never cleared:
// Interval runs forever, even after module unload
setInterval(() => refreshModels(), 60000)Bus.subscribe (github.ts)
The unsubscribe function returned by Bus.subscribe() is not captured:
// Subscription can never be unsubscribed
Bus.subscribe(Event, handler)Impact
- Timeouts continue running after errors
- Intervals run indefinitely
- Subscriptions cannot be cleaned up
Relates to #5363
Expected Behavior
- Timeouts should be cleared in finally blocks
- Intervals should be cleared on process exit
- Subscription unsubscribe functions should be captured
Activity
github-actions commentedon Jan 17, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
sauerdaniel commentedon Feb 16, 2026
Status: fix is implemented in PR #9148. Remaining blocker is CI on
e2e (windows)(NotFoundError), which cascades to the linux gate.thdxr commentedon Apr 2, 2026
Closing in favor of #20695 where we're collecting all memory-related problems. Please follow that issue for updates.