memory leaks - using windbg to tune a asp.net app's performance find so many objects not be released -
i host asp.net(v4.0.30319) app on iis7, , using following windbg command find manay objects not released gc.
!dumpheap -type xxxx 000000.... 671 246928 xxxx
xxxx objects type's name , amount of objects increased 10+/m. can't find increase when use ants memoery prfiler 8. , can't find memory leaks when using windows performance monitor. i'm superised it's windbg's problem or .get latency gc mode applied?
any body can give me advice?
thanks lot.
gary
not answer, long comment
the ants memory profiler garbage collection in order avoid false positives. windbg provides view on current situation on .net heap, garbage collector may not have run.
how many windbg snapshots did compare? number increase or decrease sometimes?
in garbage collection generation objects? find start address using
!eeheap -gc
and
!dumpheap -stat -type xxxx <gc_generation_start_address>
for different generations. if have many objects in generation 2, not collected more.
are objects rooted or candidates garbage collection? try
!gcroot <object address>
Comments
Post a Comment