To put it another way, a memory leak arises from a particular kind of programming error, and without access to the program code, someone seeing symptoms can only guess that there might be a memory leak. It would be better to use terms such as "constantly increasing memory use" where no such inside knowledge exists.
techrepublic.com.com/5208-6230-0.html?forumID=101&threa... techrepublic.com.com/5208-6230-0.html?forumID=101&threadID=214861&start=0
The following sections provide you with information and guidelines for memory leak detection and isolation on the automotive platform. Testers can use this information to become familiar with the concept of a memory leak and to take steps to locate a memory leak on the system.
msdn.microsoft.com/en-us/library/ms859400.aspx
This topic applies to: ... A small memory leak that occurs only once may not be noticed, but programs that leak large amounts of memory, or leak progressively, may display symptoms ranging from poor (and gradually decreasing) performance to running out of memory completely.
msdn.microsoft.com/en-us/library/x98tx3cf(VS.80).aspx
GlowCode is a complete real-time performance and memory profiler for Windows and .NET programmers who develop applications with C++, C#, or any .NET Framework language.
www.glowcode.com/
Some of the problems that cause memory leaks are writing or reading beyond an allocated memory segment or trying to free memory that has already been freed. A memory leak occurs when memory is allocated and not freed after use, or when the pointer to a memory allocation is deleted, rendering the memory no longer usable.
www.linuxjournal.com/article/6059
Many Mozilla community members, including both volunteers and Mozilla Corporation employees, have been helping to reduce Firefox's memory usage and fix memory leak bugs lately. ... tester Says: September 20th, 2007 at 10:51 pm...
www.squarefree.com/2007/09/20/firefox-memory-usage-and-... www.squarefree.com/2007/09/20/firefox-memory-usage-and-memory-leak-news/
Update 2007-11-06: see also my more recent post on this topic, Firefox memory usage and memory leak news, from September 2007. ... Two memory leak bugs were fixed in Firefox 1.5.0.1, released earlier this week:
www.squarefree.com/2006/02/04/memory-leak-progress/ www.squarefree.com/2006/02/04/memory-leak-progress/
To me, letting code with memory leaks out the door is the mark of an amateur. Some disagree with me. For those who agree with me, I offer "how to eliminate memory leak". To serve those who disagree with me, I offer "The Top Ten Excuses for Memory Leak".
www.troubleshooters.com/codecorn/memleak.htm www.troubleshooters.com/codecorn/memleak.htm
A lot of people complain about the Firefox "memory leak(s)". All versions of Firefox no doubt leak memory - it is a common problem with software this complicated. We look to fix the issues where we can. David Baron and others have done a huge amount of excellent work in this area.
weblogs.mozillazine.org/ben/archives/009749.html
LeakTracer uses gdb to print out the exact line where the memory was allocated and not freed - this of course means you have to free all dynamically allocated data. LeakTracer also overrides the global operator new ... ccmalloc - Shows full function traceback; valgrind - powerful tool combines strace/efence/leak tracing;
www.andreasen.org/LeakTracer/ www.andreasen.org/LeakTracer/
Definitions