Internet Explorer 9 Silverlight 4内存泄漏

Question

我们正在将视频从ASHX实现了Ihttpasynchandler到我们的Silverlight客户端。

在客户端上，Async处理程序正在使用MediaStreamSource的实现。

所有在最新的Firefox，Chrome和Internet Explorer 8中运行正常。

但在Internet Explorer中，我们看到内存泄漏。我一直在使用umdh来调试内存，并找到了一个在转储内存之间使用127MB的CallStack。所以我想我已经把它缩小到这个Callstack。

但现在我现在不知道继续我的调试。这是UMDH信息：

首先比较第一次运行和第二个

+ 117440512 ( 134217712 - 16777200)      1 allocs   BackTrace121282BC
+       0 (      1 -      1)    BackTrace121282BC   allocations

ntdll!RtlAllocateHeap+00000274
npctrl!???+00000000 : 56FE1A65
npctrl!DllCanUnloadNow+000157F0
npctrl!???+00000000 : 56FF477E
npctrl!???+00000000 : 56FF48D5
urlmon!CBSCHolder::OnDataAvailable+0000003A
urlmon!CBinding::CallOnDataAvailable+0000002B
urlmon!CBinding::OnDataNotification+000000D7
urlmon!CBinding::OnTransNotification+000001DB
urlmon!CBinding::ReportData+00000085
urlmon!COInetProt::ReportData+0000006E
mscorie!CorFltr::ReportData+0000002B
urlmon!CTransaction::DispatchReport+0000037A
urlmon!CTransaction::OnINetCallback+000000DB
urlmon!TransactionWndProc+00000028
USER32!InternalCallWinProc+00000023
USER32!UserCallWinProcCheckWow+00000109
USER32!DispatchMessageWorker+000003BC
USER32!DispatchMessageW+0000000F
IEFRAME!CTabWindow::_TabWindowThreadProc+00000722
IEFRAME!LCIETab_ThreadProc+00000317
iertutil!CIsoScope::RegisterThread+000000AB
IEFRAME!Detour_DefWindowProcA+0000006C
kernel32!BaseThreadInitThunk+0000000E
ntdll!__RtlUserThreadStart+00000070
ntdll!_RtlUserThreadStart+0000001B

.

第二运行callstack

+ 7fffff0 ( 7fffff0 -     0)      1 allocs  BackTrace121282BC
+       1 (     1 -     0)  BackTrace121282BC   allocations

ntdll!RtlAllocateHeap+00000274
npctrl!???+00000000 : 56FE1A65
npctrl!DllCanUnloadNow+000157F0
npctrl!???+00000000 : 56FF477E
npctrl!???+00000000 : 56FF48D5
urlmon!CBSCHolder::OnDataAvailable+0000003A
urlmon!CBinding::CallOnDataAvailable+0000002B
urlmon!CBinding::OnDataNotification+000000D7
urlmon!CBinding::OnTransNotification+000001DB
urlmon!CBinding::ReportData+00000085
urlmon!COInetProt::ReportData+0000006E
mscorie!CorFltr::ReportData+0000002B
urlmon!CTransaction::DispatchReport+0000037A
urlmon!CTransaction::OnINetCallback+000000DB
urlmon!TransactionWndProc+00000028
USER32!InternalCallWinProc+00000023
USER32!UserCallWinProcCheckWow+00000109
USER32!DispatchMessageWorker+000003BC
USER32!DispatchMessageW+0000000F
IEFRAME!CTabWindow::_TabWindowThreadProc+00000722
IEFRAME!LCIETab_ThreadProc+00000317
iertutil!CIsoScope::RegisterThread+000000AB
IEFRAME!Detour_DefWindowProcA+0000006C
kernel32!BaseThreadInitThunk+0000000E
ntdll!__RtlUserThreadStart+00000070
ntdll!_RtlUserThreadStart+0000001B

.

Answer 1

Have you already solved your problem?

Have you checked SL memory debugging tips such as:

http://radheyv.blogspot.cz/2011/04/detecting-memory-leaks-in-silverlight.html#!/2011/04/detecting-memory-leaks-in-silverlight.html

http://blogs.msdn.com/b/slperf/archive/2010/08/19/analyzing-silverlight-memory-usage-part-1-obtaining-measurements.aspx

http://dllshepherdnotes.blogspot.cz/2011/02/silverlight-memory-leak-part-4.html#!/2011/02/silverlight-memory-leak-part-4.html

http://www.dllshepherd.net/2011/02/silverlight-memory-leak-part-2.html