Code on stack

Memory profiling for .NET developers

Moderators: Luke Jefferson, StephenC, AndrewH, melvyn.harbour, james.billings, Laura Morley, dene.boulton

Code on stack

Postby KartikLata » Thu May 31, 2012 7:17 am

While profiling my application, I see that a disposed object is retained because inspite of clearing the event handlers subscriptions, the current code is on stack and because of this the instance is tied & cannot be reclaimed. As per Instance Retention Graph, i see that the object falls under this category:
The object under this one in the graph is a GC root because it is on the stack, having been put on the stack by bz.d().
How can I ensure that the object is reclaimed?
Posts: 1
Joined: Thu May 31, 2012 7:14 am

Postby james.billings » Fri Jun 01, 2012 10:36 am

Thanks for your post.

Based on the information supplied I'm afraid we can't possibly make any suggestion - we don't know anything about your application and we've not seen the results from your profiling.

I'm happy to take a look at your profiling results, if you can zip them up and email them to quoting F0060481 in the subject line. Once we see the results, we may be able to make some suggestions of where you should look.
Posts: 1144
Joined: Wed Jun 16, 2010 11:10 am
Location: My desk.

Return to ANTS Memory Profiler 7

Who is online

Users browsing this forum: No registered users and 1 guest