Linked by Thom Holwerda on Thu 26th Jan 2006 18:58 UTC, submitted by anonymous
Java "While programs in the Java language are theoretically immune from memory leaks, there are situations in which objects are not garbage collected even though they are no longer part of the program's logical state. This article shows you how Soft references, like weak references, can help applications prevent object loitering by enlisting the aid of the garbage collector in making cache eviction decisions."
Permalink for comment 90050
To read all comments associated with this story, please click here.
RE[4]: Singack and heave
by CrLf on Fri 27th Jan 2006 19:21 UTC in reply to "RE[3]: Singack and heave"
Member since:

It seems that *you* didn't understand it.

The problems described in the article are just bad programming, and can't be solved by a garbage collector.

The real problem are people who think that garbage collection fixes bad programming practices, or that it makes the problem of memory management completely go away.

Reply Parent Score: 1