How do I tell which mod is doing a memory leak, or if it's having a memory leak?

[smjjames]

What the question says, and besides trial and error by putting things into the near-stock branch. I'm trying to reproduce a memory leak that I've had with Moho and Ike on a near-stock branch install but it doesn't seem to be happening and I've got lots of mods on the main save.

Edit: I do have GCmonitor, so theres that.

Edit2: Okay..... I'm not seeing the memory leak on Ike. I suspect maybe something with the heating overlay?..........

Edited May 30, 2015 by smjjames

[Kerbas_ad_astra]

The heating overlay is (in 1.0.2, supposed to be fixed in 1.0.3) a known source of a memory leak. There's some kind of edge-highlighting option that can be disabled to prevent it from leaking, or it can be disabled manually via Mod+F10 (or just F10, I forget which), or with e.g. Temperature Gauge Killer.

[SAI Peregrinus]

While this is likely the PPFX edge highlighting bug, for future reference the way to tell is to do a binary search.

If using CKAN you can import/export your installed mods list, that makes things easier.

1. Anyway, make a list of your currently installed mods.

2. Remove half.

3. Test for the bug.

4a. If it's present, go to step 1. (or stop if there's only 1 mod left).

4b. If it's not present, swap halves and go to step 1.

Since each step removes half the mods it's an efficient search.

[smjjames]

PPFX is disabled anyway because the hardware doesn't support it, and I don't use CKAN.

[SAI Peregrinus]

PPFX is disabled anyway because the hardware doesn't support it, and I don't use CKAN.

CKAN just makes listing your mods (and ensuring library mods don't get uninstalled) easier, it's totally unnecessary for doing a binary search.