Memory profiling for .NET developers
Moderators: StephenC, Alex.Davies, AndrewH, melvyn.harbour
I trialed the mem profiler a few months ago, and it worked great (v5.1 I think). I just purchased the product (5.2 latest version), and now when I try to profile the same application, my application dies when I take a snapshot. The snapshot works with some of the views, but not the ones that I need to find problems with. The application is a WPF application built on .NET 3.5 SP1, running in Windows7.
- Posts: 1
- Joined: Sat Feb 20, 2010 8:09 pm
We have the same issue with 5.2, but haven't tried 5.1, is it possible to get a download of a previous version, we would like to see if 5.1 would work for us.
- Posts: 1
- Joined: Thu Jul 15, 2010 9:27 am
I'm having the same issue here. I do my first snapshot right when Profiler starts running, but when I do the second snapshot, it throws the error:
The snapshot failed because .NET did not report every referenced object. This failure is most likely due to a bug in version 2 of the CLR that can be triggered when the garbage collector is operating in 'server mode' and the target application has many large objects.You can work around this bug by manually switching your application to the workstation garbage collector. See the MSDN documentation on the gcServer configuration option for information on how to acheive this.
at P.g(Object , EventArgs )
- Posts: 8
- Joined: Sun May 31, 2009 3:12 pm
Return to ANTS Memory Profiler Previous Versions
Who is online
Users browsing this forum: No registered users and 0 guests