I'm currently looking for a program that helps me find a small (but steady.. so running it for weeks will eventually lead to an out of memory exception) leak in one of my applications - so I'm evaluating different tools..
When I start my app with dotTrace Memory and press Dump memory, the progress starts and at about 20%, stops. If I then try to access my application, it has frozen and I get an exception prompt (same thing you'd get if you have an uncaught exception). Looking at the event log I see an error from the .NET runtime telling me
The process was terminated due to an internal error in the .NET Runtime at IP 6A5421DB (6A540000) with exit code 80131506.
One time I managed to actually take a snapshot, my quad core machine that generally idles was running at full steam becoming nearly uncontrollable as dotTrace was eating away my CPU cycles.. and that was going on for minutes (I'd expect some kind of burst... but having previously tried a competing product, the latter eventually lets up).
So, is there something I'm missing here?
It looks like a known instability of dotTrace Memory 3.5.
We have now an alpha version of next memory profiler - if you're interested in trying it, please contact me: firstname.lastname@example.org
I was today trying to search for memory bugs and I get the same excepion at the same time. Running on a W7 64bit with dotTrace build: 360.114
Also the about screen says: Built on 14-9-2010 23:18:35, that does not seem right. Or is this product really this old ?
We experience same problems, with dotTrace Memory profiler (3.5) craching right after the Dump memory button was pressed. In our case it's even a bit worse. The dotTrace Memory was purchased on the wave of good impression left after the work with dotTrace Performance. And now it cannot be used...