Link to home
Start Free TrialLog in
Avatar of Mark O'Brien
Mark O'BrienFlag for United States of America

asked on

Need the definition of concept of Windows Memory Leak, and symptoms of this elusive concept.

Need the definition of “Windows Memory Leak”, and symptoms of this elusive concept.

Hello,

I have been a Level II Helpdesk Technician [with schooling for MCSA] for three years.  I have heard about the “Windows Memory Leak”, but I don’t understand the rudiments of the concept.  I checked Webopedia and found: [A bug in a program that prevents it from freeing up memory that it no longer needs. As a result, the program grabs more and more memory until it finally crashes because there is no more memory left.]  However, I still don’t understand.  I’ve heard the term tossed around a lot and it seems to be a sort of computer industry urban legend.  I searched the DB here and see the term as it applies to other various areas.  I am trying to understand the concept itself in a basic way, and what basic symptoms/causes it has.  It seems to me that many techs blame slow pc behavior on a memory leak, but they never have any evidence.  Many issues are getting unfairly blamed on the elusive memory leak.

How does a tech know when there’s a memory leak problem?  
Can it be proved?  
How do you know?  
*Can the memory leak problem be properly isolated in the trouble-shooting steps?
What does Microsoft say about memory leaks?
What are the symptoms?
What is the fix?
ASKER CERTIFIED SOLUTION
Avatar of Exchange_Admin
Exchange_Admin

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
here are some links to articles and a utility microsoft provided for jsut this purpose.

http://www.google.com/search?hl=en&q=leakyapp.exe

basically what happens is you start a program and it keeps taking more and more memory then you close the app and it does not release the memory back to teh system essentially being lost into a black hole. then you restart the app and again it starts consuming memory.