Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: Howard R. Hansen who wrote (2316)	9/5/1998 10:57:00 PM
From: Dave Bissett	Respond to of 14778

Thanks Howard...clear. DB

To: Howard R. Hansen who wrote (2316)	9/7/1998 10:40:00 AM
From: Sean W. Smith	Read Replies (2) \| Respond to of 14778

*A memory leak occurs when a program obtains memory from the operating system for its use and then doesn't return the memory to the operating system when the program exits.* Almost. a Corrected defintition would read as follows... A memory leak occurs when a program obtains memory from the operating system for its use and then doesn't return the memory to the operating system as it executes. Even programs leaking memory will have their memory returned to the heap when the process terminates. The OS tracks which process' allocate memory so even if a program leaks when it terminates the OS can reclaim the memory as the PID for which the memory was reserved no longer exists. Leaking programs are easier to spot in NT because you can monitor process size over time and watch it grow. Generally programs that run continously like device drivers, tsr's etc cause these problems as the rest will clear up the problems when they terminate. Sean

To: Howard R. Hansen who wrote (2316)	9/8/1998 9:14:00 PM
From: The Devil Dog	Read Replies (2) \| Respond to of 14778

Very good answer Howard, still the ? is, how does one successfully systematically trouble shoot the rebel program. Is this simply a process of elimination, does that resource meter in MS help?? Do you simply eliminate the program or is rebooting your computer the only way to eliminate the problem? Is there analytical tool that will source your biggest memory leaks? Ooooooh! Way to many ?'s, sorry about that. Any help is appreciated. Best Regards WB