We are a long time user of dottrace and have recently been having trouble with the memory analyzer when trying to look profile our large memory footprint application.
We are running the latest version (3.5) of the memory profiler in 64 bit mode but dottrace is just unable to handle the amount of memory and complains about running out of memory, meaning it is almost completely useless for us at the moment.
Our machines have more than enough RAM, around (8GB) and when we are profiling our app is using only about 2GB.
Getting more RAM for finding the leaks is not a concern for us, but it seems as if dottrace doesn't and is not able to use it.
My question is, is this memory issue being looked at for the next version of dottrace?
And when abouts could we see this resolved? will this be addressed in a beta that we can try?
Sure, memory problem for versions 3.1 and 3.5 is known.
For performance profiling it was already successfully resolved in dotTrace 4.0, but dotTrace Memory 4.0 is unfortunatelly still not ready for EAP.
So, be sure there will be no such problem in dotTrace Memory 4.0. I am not sure about the date when it will be ready for EAP.
WRB, Ivan Shakhov
the trace files are between 420 and 757MB
first got the exeptions on a 4GB machine but then
i tried loading them on a 16GB windows 7 and still the same issue
if it is a known issue that seems to go back to 2009 ??? Bad points there !
Why do you think we need memory profiling?
Hi Eric, unfortunately yes - it's an old known issue. We've had no dotMemory releases since then. I can notify you when we open EAP of next version if you wish.
that would be nice especially if it is near completion. i would even be interested in trying beta versions.
i do hope that the next version is a free upgrade on the 3.5 ;p
Ok. Please give me your email (you can write something to firstname.lastname@example.org).
As for free upgrade, we don't know yet.