I am running a double plugin in CS5 Mac (UI and Model) that intermittently reports massive memory leaks (750,000 leaks with over ten million bytes leaked--or thereabouts).
I am pretty competent at commenting out code until I find the leaks, but in this case, such an approach may take forever. Are there any tools that can be used to find out where these leaks are happening before I zero in on a certain branch?
I use PMRuntime.dylib from the memorytracker folder inside the sdk. Just replace the original one (make a backup) in your InDesign installation.
This produces a Leaks.txt file on InDesing shutdown and should help you to find the leaks more easily. Sometimes this can be tricky too though.
Thanks for the tip.
I am indeed generating a Leaks.txt file, but the information in the file is pretty cryptic. What I am looking at is something like this:
Alloc #1022272: 1296 bytes at: 0x3c000000
Alloc #869035: 256 bytes at: 0x36000000
And so on. Can you point me to any documentation at all that tells me how to read it?
Mr. Descamps, I can only report what I know. The leaks are reported in the Debug version of InDesign and not in the Release version, but I suspect they happen in the Release version as well because until I found the source of the leaks the release version was highly unstable.
The Leaks file can be found in the same folder as your InDesign.exe (or app as appropriate).