What problem does it solve? Investigating memory leaks in Node.js and VS Code-style applications requires parsing massive .heapsnapshot files that often exceed JSON.parse limits, then manually diffing snapshots and tracing why objects survive garbage collection. This Skill provides parsing, comparison, and retainer-path helpers that make that investigation systematic. ## Core Features & Use Cases - Snapshot Parsing at Scale: Buffer-based and streaming parsers handle .heapsnapshot files from hundreds of megabytes to over 2 GiB without hitting Node Buffer limits. - Before/After Comparison: Diff two snapshots to surface top object groups by size and count growth, plus objects that only exist in the later snapshot. - Retainer Path Tracing: BFS over non-weak reverse edges reveals exactly what keeps a class of objects alive, skipping WeakMap red herrings. - Use Case: Given before/after snapshots of a chat session switch, compare object deltas, find that ChatModel instances survive GC, and trace the retainer path back to a RowCache template or singleton Map. ## Quick Start Analyze these two .heapsnapshot files to find which objects grew between them and trace what is retaining the leaked ChatModel instances.