Audit platform node retention, memory leaks, and steady-state memory use

[pathscale]

Objective

Aggressively audit AgencyZero plus the Blitz/TRB UI platform for node leaks, memory leaks, unnecessary retention, and opportunities to reduce steady-state and peak memory. Stable previously appeared to retain nodes that Experimental may have fixed, so compare equivalent real workflows rather than assuming either build is the baseline.

Required coverage

• Detached DOM/native nodes across mount/unmount and repeated navigation.
• Layout, style, paint, display-list, texture, SVG, shadow, and animation state teardown.
• Portals/overlays, pill menus, colour wheel motion, composer effects, and hidden panes.
• Event listeners, observers, timers, async tasks, channels, inspection/tracing buffers, and cached semantic trees.
• Tauri window/runtime resources and proxy/session lifecycle where applicable.
• Long-session RSS and allocator behavior, including open/close and repeated interaction loops.
• Stable versus Experimental comparison using the same profile-safe scripted workflow and native deep inspection.

Evidence and regression gates

For every confirmed leak or reduction, record a reproducible workflow, baseline, retained object/node category, root owner, and post-fix measurement. Add focused automated leak/performance guards with realistic thresholds; do not replace root-cause evidence with a single pixel test or jsdom heap result.

Deliverables

• Ranked findings by retained bytes/growth rate and user impact.
• Root fixes at the lowest proven owning layer.
• Repeatable native tests/benchmarks suitable for CI or scheduled platform runs.
• Before/after steady-state and repeated-cycle memory measurements.