83,000 WeakReferences too many?

Memory profiling for .NET developers

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

83,000 WeakReferences too many?

Postby George.S » Mon May 16, 2011 9:52 pm

I'm working on a large (really large) Silverlight 4 application and right now am using a popular memory profiler to look for memory leaks and understand how the app is using memory.
Each time I navigate to, and then out of, a certain portion of the app the number of WeakReferences increases by over 22,000 each time. Yes that is 22,000 and not a typo. Thus, it is not many naviagations like this to get it up to 83,000 total WeakReferences or so.
This seems like way, way too much. Can anyone deeply experienced with the Silverlight 4 Garbage Collector confirm or deny that 83,000 weak references is too much?
Thanks in advance,
Posts: 1
Joined: Mon May 16, 2011 9:42 pm

Postby ShortAngry » Tue May 17, 2011 3:27 pm

I can't say I am deeply experienced with Silverlight 4 garbage collection but there do seem to be plenty of links around the net discussing memory issues with Silverlight:

http://luisguerrero.net/en/2010/04/30/d ... lverlight/

http://www.isaaceckert.com/post/2011/01 ... Table.aspx
Posts: 14
Joined: Thu Dec 02, 2010 12:29 pm

Return to ANTS Memory Profiler 7

Who is online

Users browsing this forum: No registered users and 1 guest