Timers and connections nobody closes

Map external side effects and resource lifecycles across this application: connections, subscriptions, listeners, timers, streams, cache entries and background workers. Find unclear ownership, incomplete cleanup and operations that outlive their intended scope. Prioritize evidenced leaks or correctness risks over stylistic patterns.

What it returns

Each resource with where it is created, who should release it, and the path where it is not released.

Skip it when

Short-lived scripts and one-off server functions that keep nothing running between calls.

Changes

Changes nothing

Sessions

One session

Tools

Repository access; memory snapshots help confirm.

Also called

Side-effect and resource ownership

More in Architecture and hidden complexity.