The tests were performed with both TornTools and Tampermonkey enabled and disabled, leading to the same results.
It looks like Torn is repeatedly attaching listeners but never removing them
- Browser: Chrome Version 140.0.7339.81 (Official Build) (64-bit)
- Operating System: Windows 11 Pro 24H2
- Hardware: AMD Ryzen 5 5600X 6-Core Processor (3.70 GHz), 48 GB RAM
Findings from Chrome DevTools
- EventListener objects: Count increases continuously (thousands retained).
- system / Context and (compiled code): Retained size grows over time.
- polyfill.min.js: References found holding async tasks (asap, clearImmediate) that never clear.
- Window / https://www.torn.comretains/ objects globally, preventing garbage collection.
This strongly suggests a memory leak:
- Event listeners are attached repeatedly without removal.
- Asynchronous tasks keep accumulating, blocking garbage collection.
Snapshot 1: Normal memory usage.
Snapshot 2 (after 20–30 minutes):
- Large growth in EventListener objects.
- Growth in system / Context and (compiled code).
- Retained references in polyfill.min.js.