Authorization Manager, ASP.NET, possible memory leak

From: John (noSpam_at_SendNoSpamToMe.com)
Date: 12/15/04


Date: Wed, 15 Dec 2004 13:41:41 -0500

We are using Authorization Manager in an ASP.NET application. We are using
Microsoft.Interop.Security.AzRoles. We appear to have a memory leak when
calling the method InitializeClientContextFromName. In a simulation, when we
call this method 1000 times, the LSASS process consumes more and more memory
and does not release it until the application pool is recycled. Has anyone
had an issue with Memory and Authorization Manager in ASP.NET?

John



Relevant Pages

  • Authorization Manager, ASP.NET, possible memory leak
    ... Dominick Baier - DevelopMentor ... We are using Authorization Manager in an ASP.NET application. ... calling the method InitializeClientContextFromName. ... the LSASS process consumes more and more memory ...
    (microsoft.public.dotnet.security)
  • Authorization Manager, ASP.NET, memory leak, InitializeClientContextFromName
    ... We are using Authorization Manager in an ASP.NET application. ... calling the method InitializeClientContextFromName. ... the LSASS process consumes more and more memory ...
    (microsoft.public.platformsdk.security)
  • Authorization Manager, ASP.NET, possible memory Leak
    ... We are using Authorization Manager in an ASP.NET application. ... calling the method InitializeClientContextFromName. ... the LSASS process consumes more and more memory ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Authorization Manager, ASP.NET, possible memory leak
    ... We are using Authorization Manager in an ASP.NET application. ... calling the method InitializeClientContextFromName. ... the LSASS process consumes more and more memory ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Authorization Manager, ASP.NET, possible memory Leak
    ... thread there and see if any progress has been made. ... We appear to have a memory leak when ... > calling the method InitializeClientContextFromName. ... > had an issue with Memory and Authorization Manager in ASP.NET? ...
    (microsoft.public.dotnet.framework.aspnet.security)