Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Managed C++/CLI
  4. Handle leak in application complied with CLR option.

Handle leak in application complied with CLR option.

Scheduled Pinned Locked Moved Managed C++/CLI
csharpc++dotnetwcf
1 Posts 1 Posters 3 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    atm menon
    wrote on last edited by
    #1

    In my C++ application, I have added CLR support((/clr) to use WCF communication. Everything is working well, but i observed handle leak. When I analyze this with WinDbg(!htrace). Its shows handle leaks in .NET libs as shown below. 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!ClrCr

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups