处理.NET Libs中发现的泄漏 [英] Handle leak observed in .NET Libs

问题描述

我们在CLR应用程序中观察到了句柄泄漏并使用WinDbg（！htrace）进行了分析。它显示处理.NET库中的泄漏 

句柄= 0x0000000000003300 - OPEN

线程ID = 0x0000000000004dbc，进程ID = 0x000000000000414c



0x000000007785a30a：ntdll！ZwCreateThreadEx + 0x000000000000000a

0x000007fefd37ac73：KERNELBASE！CreateRemoteThreadEx + 0x0000000000000163

0x00000000776e57a6：KERNEL32！Cre​​ateThread + 0x0000000000000036

0x000007fedaf3f0aa：clr！ClrCreateManagedInstance + 0x000000000001ae0a

0x000007fedaf3efb8：clr！ClrCreateManagedInstance + 0x000000000001ad18

0x000007fedaf3f5e3：clr！ClrCreateManagedInstance + 0x000000000001b343

0x000007fedaf3f623：clr！ClrCreateManagedInstance + 0x000000000001b383

0x000007fedaeb3b5e：clr！PreBindAssemblyEx + 0x0000000000007e5e

0x000007fedae0a05f：clr！LogHelp_LogAssert + 0x000000000000525f

0x000007fedae0837c：clr！LogHelp_LogAssert + 0x000000000000357c

0x000007fedae08125：clr！LogHelp_LogAssert + 0x0000000000003325

------------------ --------------------

句柄= 0x00000000000032fc - OPEN

线程ID = 0x0000000000004dbc，进程ID = 0x000000000000414c



0x0000000077859d0a：ntdll！ZwCreateEvent + 0x000000000000000a

0x000007fefd372d15：KERNELBASE！CreateEventExW + 0x0000000000000065

0x000007fedaf3db8a：clr！ ClrCreateManagedInstance + 0x00000000000198ea

0x000007fedaf3dd27：clr！ClrCreateManagedInstance + 0x0000000000019a87

0x000007fedaf3f077：clr！ClrCreateManagedInstance + 0x000000000001add7

0x000007fedaf3efb8：clr！ClrCreateManagedInstance + 0x000000000001ad18

0x000007fedaf3f5e3：clr！ClrCreateManagedInstance + 0x000000000001b343

0x000007fedaf3f623：clr！ClrCreateManagedInstance + 0x000000000001b383

0x000007fedaeb3b5e：clr！PreBindAssemblyEx + 0x0000000000007e5e

0x000007fedae0a05f：clr！LogHelp_LogAssert + 0x000000000000525f

0x000007fedae0837c：clr！LogHelp_LogAssert + 0x000000000000357c

0x000007fedae08125：clr！LogHelp_LogAssert + 0x0000000000003325

0x000007fedaeb5abf：clr！PreBindAssemblyEx + 0x0000000000009dbf

0x00000000776e571d：KERNEL32！BaseThreadInitThunk + 0x000000000000000d

------------------------- -------------

句柄= 0x00000000000032f8 - OPEN

线程ID = 0x0000000000004dbc，进程ID = 0x000000000000414c



0x0000000077859d0a：ntdll！ZwCreateEvent + 0x000000000000000az

0x000007fefd372d15：KERNELBASE！CreateEventExW + 0x0000000000000065

0x000007fedaf3db8a：clr！ClrCreateManagedInstance + 0x00000000000198ea

0x 000007fedaf3dd19：clr！ClrCreateManagedInstance + 0x0000000000019a79

0x000007fedaf3f077：clr！ClrCreateManagedInstance + 0x000000000001add7

0x000007fedaf3efb8：clr！ClrCreateManagedInstance + 0x000000000001ad18

0x000007fedaf3f5e3：clr！ClrCreateManagedInstance + 0x000000000001b343

0x000007fedaf3f623：clr！ClrCreateManagedInstance + 0x000000000001b383

0x000007fedaeb3b5e：clr！PreBindAssemblyEx + 0x0000000000007e5e

0x000007fedae0a05f：clr！LogHelp_LogAssert + 0x000000000000525f

0x000007fedae0837c：clr！LogHelp_LogAssert + 0x000000000000357c

0x000007fedae08125：clr！LogHelp_LogAssert + 0x0000000000003325

0x000007fedaeb5abf：clr！PreBindAssemblyEx + 0x0000000000009dbf

0x00000000776e571d：KERNEL32！BaseThreadInitThunk + 0x000000000000000d

----------------------------------- ---
$ $ $ $ $ $ $ $ $ $ $ $ $ $ $字体大小：14px的;垂直对齐：基线;列表样式类型：无;颜色：＃666666; font-family：'Segoe UI'，Helvetica，Garuda，Arial，sans-serif">

使用VS 2015和.Net版本是4.5.2。

这是.NET中的一个问题，如下所示？

https://support.microsoft.com/en-in/help/2973904/event-handle-leaks-in-a-net-framework-基于4的应用程序

如果您有任何帮助或建议，我们将不胜感激，谢谢。

Arun

解决方案

嗨arunmenons，

感谢您在此发帖。

看起来一样。但是公告告诉我们这个问题修复了  Microsoft .NET Framework 4.5。据我所知，.4.5.2不会出现此问题。

您可以联系Microsoft支持获得进一步的帮助。

https://support.microsoft.com/ en-in / contactus /

最好的问候，

Wendy

We have observed handle leak in my CLR application and analyzed with WinDbg(!htrace). Its shows handle leaks in .NET libs 

Handle = 0x0000000000003300 - OPEN
Thread ID = 0x0000000000004dbc, Process ID = 0x000000000000414c

0x000000007785a30a: ntdll!ZwCreateThreadEx+0x000000000000000a
0x000007fefd37ac73: KERNELBASE!CreateRemoteThreadEx+0x0000000000000163
0x00000000776e57a6: KERNEL32!CreateThread+0x0000000000000036
0x000007fedaf3f0aa: clr!ClrCreateManagedInstance+0x000000000001ae0a
0x000007fedaf3efb8: clr!ClrCreateManagedInstance+0x000000000001ad18
0x000007fedaf3f5e3: clr!ClrCreateManagedInstance+0x000000000001b343
0x000007fedaf3f623: clr!ClrCreateManagedInstance+0x000000000001b383
0x000007fedaeb3b5e: clr!PreBindAssemblyEx+0x0000000000007e5e
0x000007fedae0a05f: clr!LogHelp_LogAssert+0x000000000000525f
0x000007fedae0837c: clr!LogHelp_LogAssert+0x000000000000357c
0x000007fedae08125: clr!LogHelp_LogAssert+0x0000000000003325
--------------------------------------
Handle = 0x00000000000032fc - OPEN
Thread ID = 0x0000000000004dbc, Process ID = 0x000000000000414c

0x0000000077859d0a: ntdll!ZwCreateEvent+0x000000000000000a
0x000007fefd372d15: KERNELBASE!CreateEventExW+0x0000000000000065
0x000007fedaf3db8a: clr!ClrCreateManagedInstance+0x00000000000198ea
0x000007fedaf3dd27: clr!ClrCreateManagedInstance+0x0000000000019a87
0x000007fedaf3f077: clr!ClrCreateManagedInstance+0x000000000001add7
0x000007fedaf3efb8: clr!ClrCreateManagedInstance+0x000000000001ad18
0x000007fedaf3f5e3: clr!ClrCreateManagedInstance+0x000000000001b343
0x000007fedaf3f623: clr!ClrCreateManagedInstance+0x000000000001b383
0x000007fedaeb3b5e: clr!PreBindAssemblyEx+0x0000000000007e5e
0x000007fedae0a05f: clr!LogHelp_LogAssert+0x000000000000525f
0x000007fedae0837c: clr!LogHelp_LogAssert+0x000000000000357c
0x000007fedae08125: clr!LogHelp_LogAssert+0x0000000000003325
0x000007fedaeb5abf: clr!PreBindAssemblyEx+0x0000000000009dbf
0x00000000776e571d: KERNEL32!BaseThreadInitThunk+0x000000000000000d
--------------------------------------
Handle = 0x00000000000032f8 - OPEN
Thread ID = 0x0000000000004dbc, Process ID = 0x000000000000414c

0x0000000077859d0a: ntdll!ZwCreateEvent+0x000000000000000az
0x000007fefd372d15: KERNELBASE!CreateEventExW+0x0000000000000065
0x000007fedaf3db8a: clr!ClrCreateManagedInstance+0x00000000000198ea
0x000007fedaf3dd19: clr!ClrCreateManagedInstance+0x0000000000019a79
0x000007fedaf3f077: clr!ClrCreateManagedInstance+0x000000000001add7
0x000007fedaf3efb8: clr!ClrCreateManagedInstance+0x000000000001ad18
0x000007fedaf3f5e3: clr!ClrCreateManagedInstance+0x000000000001b343
0x000007fedaf3f623: clr!ClrCreateManagedInstance+0x000000000001b383
0x000007fedaeb3b5e: clr!PreBindAssemblyEx+0x0000000000007e5e
0x000007fedae0a05f: clr!LogHelp_LogAssert+0x000000000000525f
0x000007fedae0837c: clr!LogHelp_LogAssert+0x000000000000357c
0x000007fedae08125: clr!LogHelp_LogAssert+0x0000000000003325
0x000007fedaeb5abf: clr!PreBindAssemblyEx+0x0000000000009dbf
0x00000000776e571d: KERNEL32!BaseThreadInitThunk+0x000000000000000d
--------------------------------------
Handle = 0x00000000000032f4 - OPEN

Am using VS 2015 and .Net version is 4.5.2.

Is this an issue in .NET like below?

https://support.microsoft.com/en-in/help/2973904/event-handle-leaks-in-a-net-framework-4-based-application

Any help and or suggestions you may have would be greatly appreciated, Thanks.

Arun

解决方案

Hi arunmenons,

Thank you for posting here.

It looks same. But the announcement tells us this the issue fixed in Microsoft .NET Framework 4.5. As i know, the .4.5.2 would not get this issue.

You could contact Microsoft Support to get further help.

https://support.microsoft.com/en-in/contactus/

Best Regards,

Wendy

这篇关于处理.NET Libs中发现的泄漏的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！