Identify Which Mod Is Causing a Memory Leak

Use CTL's Culprit Analysis

When Calm The Leaks detects a real memory leak, it doesn't just flag the problem—it analyzes which mod is most likely responsible. This is crucial in modpacks where dozens of mods run simultaneously.

Steps:

1. Open the chat and run /ctl leaks to see all currently tracked leaks with confidence levels

2. Look for leaks marked as high confidence—these are real problems, not false positives

3. Each leak entry will show the suspected mod or component causing it

4. Run /ctl explain <leak_id> to get detailed reasoning about why that mod is suspected

5. Check the leak's growth trend—rapidly growing leaks are more urgent than slow ones

Next Steps

Once you've identified the culprit mod, you can:

• Check if an update is available for that mod
• Report the leak to the mod's issue tracker with CTL's confidence data
• Temporarily disable the mod to confirm it's the source
• Use the Spark profiling data CTL auto-triggers to provide developers with concrete evidence