V8 .heapsnapshot & Retainer Graph Dominator Engine
Calculates Shallow vs. Retained Size using Dominator Tree traversal to pinpoint why a 64-byte object retains 200MB.
Presets:
Total Nodes / Objects
5
4 referencing pointers
Total Heap Allocated
175.48 MB
Shallow memory footprint
Dominant Retained Leak
175.48 MB
(GC Roots) (100%)
Dominator Tree Depth
0 hops
Distance from active GC Roots
Dominator Nodes (Ranked by Retained Size)
| Object / Constructor | Type | Shallow | Retained Size | % Heap | GC Dist |
|---|---|---|---|---|---|
| (GC Roots)@1 | synthetic | 0 B | 175.48 MB | 100% | 0 |
| activeSessions@100 | object | 64 B | 175.48 MB | 100% | 1 |
| table@101 | array | 1 KB | 175.48 MB | 100% | 2 |
| UserSession@102 | object | 128 B | 175.48 MB | 100% | 3 |
| JWTAuthPayload@103 | string | 175.48 MB | 175.48 MB | 100% | 4 |
Retainer Path (GC Roots to Target)
Selected Object:(GC Roots)
Shallow Size (Self):0 B
Retained Size (Graph):175.48 MB
Retainer Ratio:184,001,216x amplification
Reference Path from GC Roots:
1
(GC Roots)GC ROOTLEAK TARGET
Architectural Dominator Warning: Severing the reference at
GC Root will release the entire 175.48 MB subgraph during the next V8 Scavenge/Mark-Sweep cycle.