|
Quick Lists
|
|
Bug ID:
|
6820167
|
|
Votes
|
0
|
|
Synopsis
|
GCALotAtAllSafepoints + FullGCALot(ScavengeALot) options crash JVM
|
|
Category
|
hotspot:garbage_collector
|
|
Reported Against
|
|
|
Release Fixed
|
hs16(b05),
7(b63) (Bug ID:2179582)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
6832475
,
6852342
|
|
Submit Date
|
20-MAR-2009
|
|
Description
|
SPECjbb2005 intermittently crashes VM when started with
-XX:+GCALotAtAllSafepoints -XX:+ScavengeALot(or -XX:+FullGCALot) options.
There are two different assertions to fail.
1. In the case CMS GC is used (-XX:+UseConcMarkSweepGC) the following assertion fails.
> # Internal Error (/export/users2/rbouchma/ws/hotspot/src/share/vm/gc_implementation/shared/vmGCOperations.cpp:71), pid=6723, tid=2305843011631592064
> # Error: assert(Thread::current()->is_Java_thread(),"just checking")
2. The second assertion
> # Error: assert(!Heap_lock->owned_by_self(),"this thread should not own the Heap_lock")
fails in two different locations depending on GC selected:
> hotspot/src/share/vm/memory/genCollectedHeap.cpp:744
> hotspot/src/share/vm/gc_implementation/parallelScavenge/parallelScavengeHeap.cpp:717
Posted Date : 2009-03-20 14:57:32.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
Under test and review.
Posted Date : 2009-06-08 23:43:30.0
http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/821269eca479
Posted Date : 2009-06-11 22:22:52.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
