Tracking memory leaks - UMDH Log shows IJW double thunk call stacks

See more:

memory

I am trying to track memory leaks in our application using UMDH. We have a mix of MFC/C++, Managed C++ (C++ DLLs with /clr option) and C# assemblies. The application is built with VS2012 with target framework set to 4.0.

The UMDH comparison result log shows large heap allocations as below. I understand they are related to IJW double thunking. Will they cause memory leaks or do they get allocated/de-allocated automatically ?

+ 75696 ( 229744 - 154048) 173 allocs BackTraceA9A00C0
+ 57 ( 173 - 116) BackTraceA9A00C0 allocations

ntdll!RtlAllocateHeap+00000274
clr!EEHeapAlloc+0000002C
clr!EEHeapAllocInProcessHeap+0000005B
clr!operator new+0000000E
clr!SetupThread+0000023C
clr!SetupThread+0000000D
clr!IJWNOADThunk::FindThunkTarget+00000016
clr!IJWNOADThunkJumpTargetHelper+0000000B
clr!IJWNOADThunkJumpTarget+00000043
mfc110u!_AfxThreadEntry+00000102
MSVCR110!_beginthreadex+000000B4
MSVCR110!_endthreadex+00000102
KERNEL32!BaseThreadInitThunk+0000000E
ntdll!__RtlUserThreadStart+00000070
ntdll!_RtlUserThreadStart+0000001B

+ 40812 ( 123868 - 83056) 173 allocs BackTraceA9A0154
+ 57 ( 173 - 116) BackTraceA9A0154 allocations

ntdll!RtlAllocateHeap+00000274
clr!EEHeapAlloc+0000002C
clr!EEHeapAllocInProcessHeap+0000005B
clr!Thread::Thread+000003E3
clr!SetupThread+00000251
clr!SetupThread+0000000D
clr!IJWNOADThunk::FindThunkTarget+00000016
clr!IJWNOADThunkJumpTargetHelper+0000000B
clr!IJWNOADThunkJumpTarget+00000043
mfc110u!_AfxThreadEntry+00000102
MSVCR110!_beginthreadex+000000B4
MSVCR110!_endthreadex+00000102
KERNEL32!BaseThreadInitThunk+0000000E
ntdll!__RtlUserThreadStart+00000070
ntdll!_RtlUserThreadStart+0000001B