RFR(S): 8141356: Explicitly stop CMS threads during VM termination.
jwha at google.com
Wed Nov 4 01:32:08 UTC 2015
Somehow I didn't receive Jon's email.
We've first noticed this on JDK8, but I think the bug is more triggered
with the tcmalloc + custom launcher.
On Tue, Nov 3, 2015 at 4:14 PM, Carsten Varming <varming at gmail.com> wrote:
> Dear Jon,
> I am pretty sure this has been that way for a long time. I have never seen
> a problem, but I would like to see Hotspot shut down its threads as well.
> On Tue, Nov 3, 2015 at 5:40 PM, Jon Masamitsu <jon.masamitsu at oracle.com>
>> Did you first see this bug in jdk8? I'm wondering if it
>> was always broken.
>> On 11/03/2015 01:14 PM, Jungwoo Ha wrote:
>> BUG: https://bugs.openjdk.java.net/browse/JDK-8141356
>> Webrev: http://cr.openjdk.java.net/~jwha/8141356/webrev.00/
>> Inside before_exit(), it says
>> // Stop concurrent GC threads
>> but GenCollectedHeap never implemented stop() method, and thus calling
>> empty SharedHeap::stop() method.
>> This causes CMS threads to run during the VM termination and ends up
>> ConcurrentMarkSweepThread::stop() is currently a dead code and never gets
>> The patch just implemented GenCollectedHeap::stop() to call
>> Can someone sponsor this patch?
>> Jungwoo Ha | Google | jwha at google.com
Jungwoo Ha | Java Platform Team | jwha at google.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-gc-dev