[Bug 150] finalizers are not run

[email protected] Sat, 16 Jul 2005 15:42:45 -0400
Newsgroups gmane.comp.java.vm.sablevm.bugs
Message-ID <[email protected]>
http://sablevm.org/bugs/show_bug.cgi?id=150

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
             Status|NEW                         |ASSIGNED



------- Additional Comments From [email protected]  2005-07-16 15:42 -------
The JVM specification does not force a VM to reclaim memory.  Even System.gc()
can be implemented as a no-op.

Furthermore, a JVM does not have to expose externally what it does internally. 
For example, a JVM can, without breaking the spec, internally "reclaim" memory
yet lie about it.  [public specification, private implementation].

So, SableVM's stand on the issue is that, currently, all of its various GCs
expose "externally" the behavior of the "gc-none" garbage collector.  [The user
program has no need to know that internally SableVM does better].

Therefore, the current behavior of not running finalizers is perfectly OK, as,
SableVM considers (externally) that no object space has been reclaimed (which is
allowed by the various specs).

This report is thus downgraded to wish list, as it is not really a "bug".




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.