dotTrace Memory can't open its own snapshot
Hi,
I am currently facing a problem with one of my applications. Somewhere is a memory leak and I wanted to use dotTrace Memory to find it.
Unfortunatelly, it is unable to open the snapshot it created itself, although it is only about 850 MB in size. I get a message saying "Not enough memory to load dump".
I am on a 64bit Win7 with 8GB of RAM.
Any hints?
Thanks,
Daniel
Please sign in to leave a comment.
Hello Daniel,
Unfortunately it's a known issue of dotTrace Memory 3.5 - it can't deal with "large" snapshots. "Large" is not only a bit file, but also a complicated snapshot with big amount of objects and connections. I can only recommend you to try to "localize" profiling as much as possible: start recording right before the moment you're suspecting a leak, and finish right after.
Hi Asia,
thanks for your answer.
However, to be honest, it is way too late.
I went with redgates profiler nearly two weeks ago after not receiving any answer here.
Daniel
I'm really sorry about that. But maybe once you'll be attracted by new version of dotTrace Memory!
When will a new version be released? 3.5 is completely useless for me in debugging a memory leak I'm having as I can't open any snapshots. It seems people have been complaining about this for years (e.g. from 2009 http://devnet.jetbrains.net/thread/285123). It feels like dotTrace Memory has been abandoned.
Hi Allon,
We have a kind of "quiet EAP" of next version - if you're interested in trying pre-release new version, please contact me by email: alexandra.rudenko@jetbrains.com.