Note that there are some explanatory texts on larger screens.

plurals
  1. PODo Small Memory Leaks Matter Anymore?
    primarykey
    data
    text
    <p>With RAM typically in the Gigabytes on all PC's now, should I be spending time hunting down all the small (non-growing) memory leaks that may be in my program? I'm talking about those holes that may be less than 64 bytes, or even a bunch that are just 4 bytes. </p> <p>Some of these are very difficult to identify because they are not in my own code, but may be in third party code or in the development tool's code, and I may not even have direct access to the source. In those cases, it would involve lengthy communication with the vendors of these products. </p> <p>I have seen the number one memory leak question here at SO: <a href="https://stackoverflow.com/questions/273209/are-memory-leaks-ever-ok">Are memory leaks ever ok?</a> and the number one answer to that, as of now voted up 85 times, is: No.</p> <p>But here I'm talking about small leaks that may take an inordinate amount of debugging, research and communication to track down.</p> <p>And I'm only talking about a simple desktop app. I understand that apps running on servers must be as tight as possible.</p> <p>So the question I am really asking is, if I know I have a program that leaks, say 40 bytes every time it is run, does that matter?</p> <p><a href="http://www.beholdgenealogy.com/img/single_drip.jpg" rel="nofollow noreferrer">A Single Drip http://www.beholdgenealogy.com/img/single_drip.jpg</a></p> <hr> <p>Also see my followup question: <a href="https://stackoverflow.com/questions/1720014/what-operating-systems-will-free-the-memory-leaks">What Operating Systems Will Free The Memory Leaks?</a></p> <hr> <p>Postscript: I just purchased <a href="http://www.eurekalog.com/" rel="nofollow noreferrer">EurekaLog</a> for my program development. </p> <p>I found <a href="http://eurekalog.blogspot.ca/2009/05/catching-memory-leaks_26.html" rel="nofollow noreferrer">an excellent article by Alexander</a>, the author of EurekaLog (who should know these things), about catching memory leaks. In that article, Alexander states the answer to my question very well and succinctly:</p> <blockquote> <p>While any error in your application is always bad, there are types of errors, which can be not visible in certain environments. For example, <a href="http://en.wikipedia.org/wiki/Memory_leak" rel="nofollow noreferrer">memory or resources leaks</a> errors are relatively harmless on client machines and <a href="http://blogs.msdn.com/oldnewthing/archive/2004/03/17/91178.aspx" rel="nofollow noreferrer">can be deadly on servers</a>.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload