Native Memory Leak In WinForms Application

[taternoe]

Hi,

We have a significant memory leak (1MB per operation) in our UI application. When I profiled the app using DotMemory I found that the leaked memory was unmanaged. Using UDMH and Windbg, I can see the leak, but the call stack (see UDMH call stack below) only points to the CLR. Any ideas on how to debug this farther would be appreciated.

Thanks,
Nate

>>>

+ 1e2a0 ( 1576b2c - 155888c) 2eb allocs BackTraceA5063C0
+ 39 ( 2eb - 2b2) BackTraceA5063C0 allocations

ntdll!RtlAllocateHeap+274
gdiplus!GpMalloc+16
gdiplus!GpMemoryBitmap::AllocBitmapData+74
gdiplus!GpMemoryBitmap::AllocBitmapMemory+26
gdiplus!GpMemoryBitmap::BeginSink+158
gdiplus!GpWicDecoder::BeginSink+31
gdiplus!GpWicDecoder:ecode+75
gdiplus!GpDecodedImage::InternalPushIntoSink+2D
gdiplus!GpDecodedImage:ushIntoSink+3C
gdiplus!GpMemoryBitmap::InitImageBitmap+15F
gdiplus!GpMemoryBitmap::CreateFromImage+51
gdiplus!CopyOnWriteBitmap::LoadIntoMemory+85
gdiplus!GpBitmap::ForceValidation+18
System.Drawing.ni!???+0 : 7468A207
System.Drawing.ni!???+0 : 746851DF
System.Drawing.ni!???+0 : 7468514D
System.Drawing.ni!???+0 : 74685073
clr!CallDescrWorkerWithHandler+6B
clr!MethodDescCallSite::CallTargetWorker+16A
clr!TryCallMethodWorker+5A
clr!TryCallMethod+66
clr!RuntimeMethodHandle::SerializationInvoke+1B8
mscorlib.ni!???+0 : 705A50F6
mscorlib.ni!???+0 : 705A4F9C
mscorlib.ni!???+0 : 705A4EC7
mscorlib.ni!???+0 : 705A01A0
mscorlib.ni!???+0 : 7059FF5B
mscorlib.ni!???+0 : 7059D307
mscorlib.ni!???+0 : 7057BB7B
mscorlib.ni!???+0 : 7057B9DC
mscorlib.ni!???+0 : 7057B9B7
mscorlib.ni!???+0 : 705C53AD

Continue reading...