Error on "Take Memory Snapshot"

Memory profiling for .NET developers

Moderators: StephenC, Alex.Davies, AndrewH, melvyn.harbour

Error on "Take Memory Snapshot"

Postby kukuwka » Thu Jul 08, 2010 12:36 pm

Hi,

When I try press "Take Memory Snapshot" I receive the next 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.
Q
at P.g(Object , EventArgs )
at T.<>c__DisplayClass16.<backer_SnapshotCompleted>b__15()
at O.b()

How can I avoid it?

Thanks,
kukuwka
kukuwka
 
Posts: 2
Joined: Thu Jul 08, 2010 12:28 pm

Postby StephenC » Thu Jul 08, 2010 1:29 pm

See the MSDN documentation on the gcServer configuration option for information on how to acheive this.

http://support.microsoft.com/kb/911716
StephenC
 
Posts: 306
Joined: Mon Oct 15, 2007 9:18 am
Location: Cambridge

Postby kukuwka » Sun Jul 11, 2010 7:26 am

Hi,
This solution is for Windows Server 2003 .
I have Windows Server 2008.

Thanks
kukuwka
 
Posts: 2
Joined: Thu Jul 08, 2010 12:28 pm

Postby StephenC » Mon Jul 12, 2010 4:31 pm

Did you still try changing the setting on Windows Server 2008?

Is it still throwing the error?

Stephen
StephenC
 
Posts: 306
Joined: Mon Oct 15, 2007 9:18 am
Location: Cambridge

Re:

Postby andegre » Thu Jul 15, 2010 7:45 pm

StephenC wrote:See the MSDN documentation on the gcServer configuration option for information on how to acheive this.

http://support.microsoft.com/kb/911716


Ok, I've read this article, but it also says that
The Workstation garbage collector is optimized for low latency. Low latency is typically required for client applications. However, low latency may cause decreased throughput after you configure the .NET Framework common language runtime to use the Workstation garbage collector.


I can't afford to run my production environment like this if we are already having performance problems. Or, are you saying to just change this setting in order for the snapshot to work?

FYI - the only way to reproduce our "memory leak" is in a production environment, we are not able to reproduce the load, or the leak in a test environment so the above suggestion may not work for me.

Please advise, thanks!
andegre
 
Posts: 8
Joined: Sun May 31, 2009 3:12 pm

Postby amcclure » Mon Aug 09, 2010 7:57 pm

I am hitting this error also:
The snapshot failed because .NET did not report every referenced object. ...

I do not always get it but seem to get always when doing a large memory operation. Can this be caused by an out of memory condition other then the one related to gcServer. I have added the gcserver enabled="false" in the machine.config and it helped. before that i always got the above error. when taking a snapshot. I am trying to profile a wcf service.
amcclure
 
Posts: 1
Joined: Mon Aug 09, 2010 6:07 pm

Postby RW » Wed Oct 05, 2011 12:30 pm

Hi,
Have u done the changes in Machine.config or ASPnet.config??
I am facing the same problem even after the change in ASPnet.config file.

Please reply. Thanks.
RW
 
Posts: 7
Joined: Tue Oct 04, 2011 2:37 pm

Postby Chris.Allen » Fri Oct 14, 2011 4:45 pm

If our current documentation is not working - would anyone be able to help us reproduce this exact issue in-house? If so, please contact support@red-gate.com directly. Thanks!
Chris.Allen
 
Posts: 594
Joined: Thu Mar 12, 2009 4:17 pm

Postby Adam Hodge » Tue Mar 06, 2012 3:01 pm

I am in the same boat! Any suggestions for Windows Server 2003?
Adam Hodge
 
Posts: 3
Joined: Tue Mar 06, 2012 2:53 pm


Return to ANTS Memory Profiler Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests