JEP 132: More-prompt finalization

Jon Masamitsu jon.masamitsu at
Fri Dec 23 08:13:24 PST 2011


 From the VM side there are two issues that I think we should understand
better before we work on an API.  Those are described in the JEP as
1) more aggressive management of the of finalization queue and 2) multiple
finalizer threads.  We should see how much of the problem can be
alleviated by either or both or by other VM side changes that occur to us
during the work and then think about what is left and what information
we want from the user to address what's left.   As Mark has said, I
think there will be a library side JEP at some point for those discussions.


On 12/22/2011 6:15 PM, David Holmes wrote:
> On 23/12/2011 9:05 AM, mark.reinhold at wrote:
>> Posted:
> hotspot-dev seems the wrong mailing list to discuss this. It is 
> primarily a Java level API. I would suggest using core-libs-dev.
> David

More information about the hotspot-dev mailing list