IBM User Guide for Java V7 on Windows > IBM SDK for Java > The collector and the allocator > How to coexist with the Garbage Collector

Bug reports

Attempts to predict the behavior of the Garbage Collector (GC) are frequent underlying causes of bug reports.

Here is an example of a regular bug report to Java™ service of the "Hello World" variety. A simple program allocates an object or objects, clears references to these objects, and then initiates a garbage collection cycle. The objects are not seen as collected. Typically, the objects are not collected because the application has attached a finalizer that does not run immediately.

It is clear from the way that the GC works that more than one valid reason exists for the objects not being seen as collected:

• An object reference exists in the thread stack or registers, and the objects are retained garbage.
• The GC has not chosen to run a finalizer cycle at this time.

See list item 1 in Garbage collection summary. Real garbage is always found eventually, but it is not possible to predict when as stated in list item 5.

Parent: How to coexist with the Garbage Collector

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.