Resolving Memory leak in Winlogon.exe

[Jnrtech]

Just needed some advice on how to resolve a memory leak on a couple of servers

they are all Windows 2003 SP1 Xeon 3.4 with 4gb of memory...

I'm getting alerts that there are memory leaks with the winlogon.exe

But I have no idea how to track down what's causing this memory leak, or how to resolve these memory leaks

looking through the forum people are suggesting perfmon... but I don't know what processes I should be tracking... to find the cause...

any help would be appreciated...

[cluberti]

You can download perfwiz from the Microsoft site to configure perfmon automatically. However, if you've got a leak in winlogon.exe, you need to tell us what kind of leak it is - is it a memory leak, a handle leak (and if so, is it a memory handle leak or a file handle leak), or is your monitoring software just too picky ?

I would rather suggest to you, that when your monitoring software is complaining about a leak in winlogon.exe, that you instead do the following:

First, install the "Debugging Tools for Windows" from:

http://www.microsoft.com/whdc/devtools/deb...installx86.mspx

Once these tools are installed, do the following:

1. Create a directory called c:\adplus

2. Open a command prompt and change to the directory where you installed the debugging tools. By default, this is "C:\Program Files\Debugging Tools for Windows"

3. Type the following command in the command prompt:

cscript adplus.vbs -hang -pn winlogon.exe -o c:\adplus

This should create a .dmp file in the C:\adplus folder - load that up in windbg or cdb and look and see what is actually running in the winlogon.exe process. If you need help with that, we've got some people here who are decent debuggers - PM me and I'll provide an upload location for you, and we can take a look.