none
Handle leak observed in .NET Libs RRS feed

  • Question

  • 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

    Thursday, May 2, 2019 9:37 AM

All replies

  • 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


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, May 3, 2019 3:35 AM
    Moderator