none
Tracking a Memory leak in managed&unmanaged code RRS feed

  • Question

  • Hi,

    I'm expiriencing a massive memory leak in a managed and unmanaged app (I hope it's the right forum for this kind of issue).

    I used DebugDiag to take & analyze a dump of the app (a relevant part of the report added below).

    In the report, you can see that the leak mainly comes from 1,326,792 allocations of 136 bytes.

    Since the call stacks doesn't show any function from my code  (mainy ntdll functions), I wonder how should I continue with my investigation.

    Any ideas or suggestions?

    Thanks.

     

    Call stack sample 1

    Address   0x77ffba60
    Allocation Time   00:05:00 since tracking started
    Allocation Size   136 Bytes


    Function   Source   Destination
    msvcr90!malloc+79   f:\dd\vctools\crt_bld\self_x86\crt\src\malloc.c @ 163   
    msvcr90!operator new+1f   f:\dd\vctools\crt_bld\self_x86\crt\src\new.cpp @ 59   msvcr90!malloc
    ntdll!RtlAllocateHeap+17c      
    ntdll!LdrpCallInitRoutine+14      
    ntdll!NtTestAlert+c      
    ntdll!_LdrpInitialize+2c1      
    ntdll!ZwContinue+c      
    kernel32!BaseThreadInitThunk+e      
    ntdll!__RtlUserThreadStart+23      
    ntdll!_RtlUserThreadStart+1b      ntdll!__RtlUserThreadStart


    Call stack sample 2

    Address   0x77ffbaf0
    Allocation Time   00:05:00 since tracking started
    Allocation Size   136 Bytes


    Function   Source   Destination
    msvcr90!malloc+79   f:\dd\vctools\crt_bld\self_x86\crt\src\malloc.c @ 163   
    msvcr90!operator new+1f   f:\dd\vctools\crt_bld\self_x86\crt\src\new.cpp @ 59   msvcr90!malloc
    0x72BC84EF      
    0x72BA9CEA      
    0x72C623ED      
    0x72CB5439      
    ntdll!RtlAllocateHeap+17c      
    ntdll!LdrpCallInitRoutine+14      
    ntdll!NtTestAlert+c      
    ntdll!_LdrpInitialize+2c1      
    ntdll!ZwContinue+c      
    kernel32!BaseThreadInitThunk+e      
    ntdll!__RtlUserThreadStart+23      
    ntdll!_RtlUserThreadStart+1b      ntdll!__RtlUserThreadStart


    Wednesday, December 22, 2010 8:06 AM

Answers

All replies