JEP 132: More-prompt finalization

[Jon Masamitsu]

Dmitry,

Before I try to answer your question, do you ever try to use
System.gc() to get finalizers to run?   If you don't because
System.gc() it too disruptive (generally being stop-the-world),
are you using CMS and have you tried using System.gc()
with -XX:+ExplicitGCInvokesConcurrent?

Jon

On 12/24/2011 4:33 AM, Dmitry Samersoff wrote:
> Jon,
>
> One of problem with finalization nowdays is that with 1 Tb heap GC (and
> thus finalization) never happens.
>
> Do you plan to address this problem?
>
> -Dmitry
>
>
> On 2011-12-23 20:13, Jon Masamitsu wrote:
>> David,
>>
>>  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.
>>
>> Jon
>>
>> On 12/22/2011 6:15 PM, David Holmes wrote:
>>> On 23/12/2011 9:05 AM, mark.reinhold at oracle.com wrote:
>>>> Posted: http://openjdk.java.net/jeps/132
>>> 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
>