Memory Leak

[Guest sirketchup9000-ng@yahoo.com]

Hello everyone,

 

I have a Windows 2003 server, Standard Edition. The server is

running Exchange 2003, all functions, including OWA. I have been

troubleshooting IIS on this machine for a bit of time now. IIS will

run fine for a few weeks and then will stop accepting new connections,

producing error messages in the httperr.log file. My troubleshooting

steps led me to a memory leak issue on the server, as described in

this article:

 

http://blogs.msdn.com/david.wang/archive/2005/09/21/HOWTO-Diagnose-IIS6-failing-to-accept-connections-due-to-Connections-Refused.aspx

 

I have been following the suggestions from David Wang and did find a

memory leak. My issue now is that I cannot determine what

application is actually causing the non-paged pool to fill up. The

memory tag in question is "Thre." This app grows by approximately 15

mb of non-paged pool utilization per day. When doing a string search

for this tag on the system too many driver files match the search,

including core windows files.

 

I have tried shutting down services, including Dell, GFI, APC, etc. I

have also updated a few. However, shutting down services of course

does not free up the non-paged pool memory. I know what the problem

is now, but just cannot trace it to a culprit. Can anyone help me

determine what application memory tag, "Thre, " actually belongs to?

 

Thank you in advance,

Dmitry Akselrod

[Guest sirketchup9000-ng@yahoo.com]

Re: Memory Leak

 

Ha! I solved my own problem. The problem was being caused by a

Watchguard utility, controldGui.exe. I was able to actually to

determine the culprit by using none other then Task Manager. I simply

added the Handle Count column to task manager, and there it was,

controldGUI.exe, with thousands of handles. I killed the process and

non-paged pool utilization went down by about 60-70 MB. I can't

believe I didn't think of this before.

 

Dmitry Akselrod

[Guest Brains,None]

Re: Memory Leak

 

No Problem! Thanks for the tip!

 

sirketchup9000-ng@yahoo.com wrote:

> Ha! I solved my own problem. The problem was being caused by a

> Watchguard utility, controldGui.exe. I was able to actually to

> determine the culprit by using none other then Task Manager. I simply

> added the Handle Count column to task manager, and there it was,

> controldGUI.exe, with thousands of handles. I killed the process and

> non-paged pool utilization went down by about 60-70 MB. I can't

> believe I didn't think of this before.

>

> Dmitry Akselrod

>