You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: skills/memory-leak-debugging/SKILL.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,3 +36,13 @@ Once you have generated `.heapsnapshot` files using `take_memory_snapshot`, use
36
36
When you have found a leak trace (e.g., via `memlab` output), you must identify the root cause in the code.
37
37
38
38
- Read [references/common-leaks.md](references/common-leaks.md) for examples of common memory leaks and how to fix them.
39
+
40
+
### 4. Fallback: Comparing Snapshots Manually
41
+
42
+
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.
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.
0 commit comments