Linked by Zachary Pinter on Tue 27th Apr 2004 17:09 UTC
General Development Garbage collection (GC) is a technology that frees programmers from the hassle of explicitly managing memory allocation for every object they create. Traditionally, the benefit of this automation has come at the cost of significant overhead. However, more efficient algorithms and techniques, coupled with the increased computational power of computers have made the overhead negligible for all but the most extreme situations.
Permalink for comment
To read all comments associated with this story, please click here.
Re: Response
by Anonymous on Wed 28th Apr 2004 03:15 UTC

Please read "Sun Certified Programmer & Developer for Java 2 Study Guide (Exam 310-035 & 310-027)" by Kathy Sierra and Bert Bates.

Their explanation of Java GC is by far the best I've read. In this they explicitly state that the JVM may do ABC or it may do DEF. And even if we reverse engineer the JVM and determine exactly how it does it we cannot be sure that the identical JVM will work that way on other OSes.

I personally have studied the the GC operations on various J2ME implementations (where memory is scarse and needs to be cleaned up often) and can say that the GC runs 90% of the time but that is due to how the vendor (KVM) implemented GC and not on Sun or the Java API.

Your explanations of GC in general are very well articulated and I don't mean to criticize. I mean only to correct you.