WinDbg - 查看 System.Web.Compilation.BuildManager 的 ResultCache

发布于 2024-10-16 10:13:56 字数 1612 浏览 9 评论 0原文

我正在调试内存泄漏。我无法重现它，但当程序在特定情况下运行时，我会得到大约 60MB/小时的稳定泄漏。几天后，当堆达到约 2GB 时，我进行转储并附加 WinDbg。

!heapdump –stat
显示有 1.2 GB 的哈希表。这大约占堆的 55%。

!dumpheap -类型 System.Collections.Hashtable+KeyCollection
给出 153,080 个 Hashtable 实例的地址。

其中一些实例的 !gcroot 表明它们全部由 Me.Logger 拥有的线程拥有。

RSP:28f67e840:Root:0000000245edb7d0(Me.Logger)->
0000000245edb9d8(System.Threading.Thread)->
00000002459b9830(System.Runtime.Remoting.Contexts.Context)->
00000002459b9548(System.AppDomain)->
0000000245a1fed0(System.ResolveEventHandler)->
00000002259697a0(System.Web.Compilation.BuildManager)->
0000000245a20120(System.Web.Compilation.MemoryBuildResultCache)->
00000002459c2a48(System.Web.Caching.CacheMultiple)->
00000002459c2a70(System.Object[])->
00000002459c7e08(System.Web.Caching.CacheSingle)->
00000002459c9008(System.Web.Caching.CacheUsage)->
00000002459c9030(System.Object[])->
00000002459c9138(System.Web.Caching.UsageBucket)->
00000001b996fba8(System.Web.Caching.UsagePage[])->
00000001ae054388(System.Web.Caching.UsageEntry[])->
0000000251576590(System.Web.Caching.CacheEntry)->
00000002515761a0(System.Web.Mobile.MobileCapabilities)->
00000002515742c8(System.Collections.Hashtable)->
0000000251576548(System.Collections.Hashtable+KeyCollection)

我不知道如何解释这个输出。看来 System.Web.Compilation.BuildManager 只是有一个巨大的缓存。

BuildManager、MobileCapability、ResolveEventHandler - 我在我的代码库中没有使用任何这些。

我是 WinDbg 的新手。我如何进一步调试这个？

我怎样才能看到哈希表中的内容？（SoS v2.0.50727 所以没有！DumpCollection）。我怎样才能看到 BuildManager 构建了什么？

原文

I'm debugging a memory leak. I cannot reproduce it, but when the program runs in specific circumstances I get a steady leak at about 60MB/hr. After several days, I take a dump when the heap is ~2GB and attach WinDbg.

!heapdump –stat
Shows there are 1.2 GB worth of Hashtables.
This is about 55% of the heap.

!dumpheap -Type System.Collections.Hashtable+KeyCollection
Gives address of the 153,080 Hashtable instances.

!gcroot of a few of these instances indicate that they are all owned by Threads owned by Me.Logger.

RSP:28f67e840:Root:0000000245edb7d0(Me.Logger)->
0000000245edb9d8(System.Threading.Thread)->
00000002459b9830(System.Runtime.Remoting.Contexts.Context)->
00000002459b9548(System.AppDomain)->
0000000245a1fed0(System.ResolveEventHandler)->
00000002259697a0(System.Web.Compilation.BuildManager)->
0000000245a20120(System.Web.Compilation.MemoryBuildResultCache)->
00000002459c2a48(System.Web.Caching.CacheMultiple)->
00000002459c2a70(System.Object[])->
00000002459c7e08(System.Web.Caching.CacheSingle)->
00000002459c9008(System.Web.Caching.CacheUsage)->
00000002459c9030(System.Object[])->
00000002459c9138(System.Web.Caching.UsageBucket)->
00000001b996fba8(System.Web.Caching.UsagePage[])->
00000001ae054388(System.Web.Caching.UsageEntry[])->
0000000251576590(System.Web.Caching.CacheEntry)->
00000002515761a0(System.Web.Mobile.MobileCapabilities)->
00000002515742c8(System.Collections.Hashtable)->
0000000251576548(System.Collections.Hashtable+KeyCollection)

I don't know how to interpret this output. It seems that System.Web.Compilation.BuildManager just has a massive cache.

BuildManager, MobileCapabilities, ResolveEventHandler - I don't use any of this in my codebase.

I am new to WinDbg. How do I debug this further?

How could I see what's in the Hashtables? (SoS v2.0.50727 so no !DumpCollection).
How could I see what BuildManager has built?

分享到QQ

分享到微博