News for hackers. Stuff that matters.
Re:How the Boehm Garbage Collector Works by eridius on Friday February 10, 2012 @04:57PM (#3577656)
Holding onto a pointer that should be freed is leaking memory.
Re:How the Boehm Garbage Collector Works by ghusbands on Friday February 10, 2012 @06:23PM (#3577951)
That is overly conservative. A perfect garbage collector that always runs in reasonable time is provably impossible. What sambeau said is that it often holds on to [an allocation] for too long, which is true to varying extent of all garbage collectors.

To leak memory is to fail to deallocate it at all.

Re:How the Boehm Garbage Collector Works by gchpaco on Friday February 10, 2012 @08:30PM (#3578261)
"Leak" may be the right word for some configurations with conservative GC. A "leak-free" GC would presumably guarantee eventual collection of all dead objects, which is impossible with a conservative GC in theory, and in practice it's not especially difficult to get into a configuration with the Boehm GC where the lifetime of a dead object is infinite (usually because it doesn't move and some binary data that the GC thinks might be a pointer doesn't go away, because it's texture data or something).
Re:How the Boehm Garbage Collector Works by sambeau on Saturday February 11, 2012 @01:16PM (#3579724)
And of course there are many valid programs where leaking memory is totally fine (and more performant): shell tools, cgis etc.

When I write any of these, the only time I free anything is when I've had to malloc something huge.

Re:How the Boehm Garbage Collector Works by cpeterso on Friday February 10, 2012 @11:53PM (#3578606)
Interestin dichotomy: In a managed system, a "leak" is when a pointer points to a memory allocation too long. In an unmanaged system, a "leak" is when you have no pointers to a memory allocation. :)