Best practice / method for finding general memory leaks

[Guest Thee Chicago Wolf]

Trying to figure out if the server or our print control app is leaking

and resulting in oddball behavior with print jobs. I have applied

post-SP2 print related patches already and they've helped tremendously

but there are still some niggling behaviors that I suspect are

attributable to leaky app behavior (i.e., works fine for 2-3 weeks

then problems begin to happen. Reboot of the server gives us 2-3 weeks

of uneventful behavior and then odd behavior again).

 

I've got no less than 19 KB articles that deal with and do patch

existing and known memory leak issues. Rather than just install all

the known hotfixes for memory leaks and cross my fingers, I'd rather

take the pragmatic, not shotgun, approach to ruling out leaks. How can

this be done globally? Traps? Currently we're on Server 2003 SE SP2

patched to Jan. 2008.

 

- Thee Chicago Wolf

[Guest Steve Goddard]

RE: Best practice / method for finding general memory leaks

 

The last time I saw this we reduced the memory available in the server and

took it in turns to watch taskmgr until we saw which process leaked the

memory and then went from there. Simple but it worked, printer driver.

 

 

--

Steve G.

MCSA 2003 +M

 

 

"Thee Chicago Wolf" wrote:

> Trying to figure out if the server or our print control app is leaking

> and resulting in oddball behavior with print jobs. I have applied

> post-SP2 print related patches already and they've helped tremendously

> but there are still some niggling behaviors that I suspect are

> attributable to leaky app behavior (i.e., works fine for 2-3 weeks

> then problems begin to happen. Reboot of the server gives us 2-3 weeks

> of uneventful behavior and then odd behavior again).

>

> I've got no less than 19 KB articles that deal with and do patch

> existing and known memory leak issues. Rather than just install all

> the known hotfixes for memory leaks and cross my fingers, I'd rather

> take the pragmatic, not shotgun, approach to ruling out leaks. How can

> this be done globally? Traps? Currently we're on Server 2003 SE SP2

> patched to Jan. 2008.

>

> - Thee Chicago Wolf

>

[Guest Thee Chicago Wolf]

Re: Best practice / method for finding general memory leaks

 

>The last time I saw this we reduced the memory available in the server and

>took it in turns to watch taskmgr until we saw which process leaked the

>memory and then went from there. Simple but it worked, printer driver.

 

Steve,

 

Yep, that's one of the suspect things I was going to investigate. It's

on the low priority level because this print server has been using the

same drivers for a while and some of these things started to manifest

after SP2 was installed in September. Cheers.

 

- Thee Chicago Wolf