Schannel Memory Leak Problem on win2003

From: Monster (monster.this_at_monster.that)
Date: 05/28/05 

Date: Sat, 28 May 2005 03:38:34 -0400

In my server application this leak doesn't occur in windows xp, however on
windows 2003 systems the umdh dump shows a large memory leak that I can't
seem to trace.

The umdh log is below. It's weird the stack trace doesn't seem to originate
anywhere from inside my code and I have all the pdbs. Any ideas what is
causing this?

+ 3212017 ( 3212017 - 0) 10859 allocs BackTrace09571
+ 1090572 ( 1090572 - 0) 2605 allocs BackTrace10651
+ 452759 ( 452759 - 0) 2782 allocs BackTrace10645

003102F1 bytes in 0x2a6b allocations (@ 0x00000030 + 0x00290EE1) by:
BackTrace09571
        ntdll!RtlAllocateHeapSlowly+00000041
        ntdll!RtlAllocateHeap+00000E3A
        rsaenh!ContAlloc+00000013
        ntdll!RtlInterlockedPopEntrySList+00000025

0010A40C bytes in 0xa2d allocations (@ 0x00000030 + 0x000EBB9C) by:
BackTrace10651
        ntdll!RtlAllocateHeapSlowly+00000041
        ntdll!RtlAllocateHeap+00000E3A
        rsaenh!ContAlloc+00000013
        rsaenh!NTagLogonUser+00000133
        rsaenh!CPAcquireContext+00000032
        ADVAPI32!CryptAcquireContextA+00000547
        ADVAPI32!CryptAcquireContextW+000000A4
        schannel!RemoteCryptAcquireContextCallback+00000085
        Secur32!LsaCallbackHandler+0000004D
        Secur32!SecpHandleCallback+0000004C
        Secur32!CallSPM+0000003F
        Secur32!SecpAcquireCredentialsHandle+00000196
        ntdll!CheckHeapFillPattern+0000003C

0006E897 bytes in 0xade allocations (@ 0x00000030 + 0x0004DEF7) by:
BackTrace10645
        ntdll!RtlAllocateHeapSlowly+00000041
        ntdll!RtlAllocateHeap+00000E3A
        kernel32!LocalAlloc+00000058
        ADVAPI32!CryptAcquireContextA+0000046A
        ADVAPI32!CryptAcquireContextW+000000A4
        schannel!RemoteCryptAcquireContextCallback+00000085
        Secur32!LsaCallbackHandler+0000004D
        Secur32!SecpHandleCallback+0000004C
        Secur32!CallSPM+0000003F
        Secur32!SecpAcquireCredentialsHandle+00000196
        ntdll!CheckHeapFillPattern+0000003C

Relevant Pages

  • Memory Leak issue
    ... MFC, COM dll, COM ocx, COM server, Windows static lib and windows dynamic ... It is also showing some of the memory leak in the MFC dlls. ... We are measuring the Private bytes for the application using Sysinternals ...
    (microsoft.public.vc.mfc)
  • Memory Leak Issue
    ... MFC, COM dll, COM ocx, COM server, Windows static lib and windows dynamic ... It is also showing some of the memory leak in the MFC dlls. ... We are measuring the Private bytes for the application using Sysinternals ...
    (microsoft.public.vc.debugger)
  • RE: Memory leak when using directshow, help!
    ... These do not get destroyed after all the directshow ... What "ActiveMovieWindow" windows do you see and are they destroyed? ... I have used the ocx to play the same files with no memory leak. ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: "Insufficient system resources exist"
    ... You have a memory leak somewhere...very hard to diagnose. ... >I am experiencing an interesting problem with system resources in Windows ... > Nothing will fix it, other than to crash out and re-boot. ... > Below is my Hijack This log: ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Lsass.exe - Not Enough Quota
    ... Windows XP issue ... You might observe a memory leak in Lsass.exe private bytes with the System ... This behavior can occur if the built-in groups (such as the Administrators ... also use the information in the following Microsoft Knowledge Base article ...
    (microsoft.public.windowsxp.help_and_support)