SIGSEGV on GCTaskThread in jdk 6u18

[Y. Srinivas Ramakrishna]

Janda Martin wrote:
> Thank you for fast response. I supposed that I use Serial GC so this problem is different.

Unless you specify it explicitly via -XX:+UseSerialGC, the GC ergonomics
might pick a different collector, and in this case it picked parallel gc
because yr machine was considered a "server class" machine (or some such)
because you had 8 cores on yr box.

> 
>   I will try ReduceInitialCardMarks

Yes either that, or explicitly specify serial gc.

In your case, since you have 8 cores, you should use -ReduceInitialCardMarks
and continue using the parallel collector you are getting by default.
Indeed you might want to specify -XX:+UseParallelOldGC which i think you
aren't getting by default (i wonder why; i thought that was the parallel
collector default now, but haven't checked recently).

-- ramki

> 
>   Martin
> 
> ----- Original Message -----
> From: "Vladimir Kozlov" <Vladimir.Kozlov at Sun.COM>
> To: hotspot-dev at openjdk.java.net
> Sent: Thursday, January 21, 2010 10:03:01 AM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna
> Subject: Re: SIGSEGV on GCTaskThread in jdk 6u18
> 
> Try -XX:-ReduceInitialCardMarks
> 
> Please, read release notes for 6u18.
> 
> Vladimir
> 
> On 1/21/10 12:24 AM, Andreas Kohn wrote:
>> On Thu, 2010-01-21 at 08:45 +0100, Janda Martin wrote:
>>> Please can you help me. I experienced several crashes on GCTaskThread in latest Java6u18 when running IntelliJ IDEA (not only). 64bit linux, 32bit jvm, 4 core processor
>>>   I create new bug report with Review ID: 1699960.
>>>
>>>    Is there any -XX options to help diagnose this problem. It looks like regression from 6u17 (maybe) or 6u16 (sure).
>> We observed a very similar 6u18 crash (once so far), 64bit linux, 64bit
>> jvm.
>>
>> I have attached our hs_err log as well.
>>
>> Regards,
>> --
>> Andreas
>>