SKILL.md
$27
- Use tools like
click,navigate_page,fill, etc., to manipulate the page into the desired state.
- Revert the page back to the original state after interactions to see if memory is released.
- Repeat the same user interactions 10 times to amplify the leak.
- Use
take_memory_snapshotto save.heapsnapshotfiles to disk at baseline, target (after actions), and final (after reverting actions) states.
2. Using Memlab to Find Leaks (Recommended)
Once you have generated .heapsnapshot files using take_memory_snapshot, use memlab to automatically find memory leaks.
- Read references/memlab.md for how to use
memlabto analyze the generated heapsnapshots.
- Do not read raw
.heapsnapshotfiles usingread_fileorcat.
3. Identifying Common Leaks
When you have found a leak trace (e.g., via memlab output), you must identify the root cause in the code.
- Read references/common-leaks.md for examples of common memory leaks and how to fix them.
4. Fallback: Comparing Snapshots Manually
If memlab is not available, you MUST use the fallback script in the references directory to compare two .heapsnapshot files and identify the top growing objects and common leak types.
Run the script using Node.js:
node skills/memory-leak-debugging/references/compare_snapshots.js <baseline.heapsnapshot> <target.heapsnapshot>The script will analyze and output the top growing objects by size and highlight the 3 most common types of memory leaks (e.g., Detached DOM nodes, closures, Contexts) if they are present.