JDK-8068484 : jnilock002 failed with assert: monitor is invalid
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9
  • Priority: P2
  • Status: Resolved
  • Resolution: Duplicate
  • Submitted: 2015-01-05
  • Updated: 2015-08-26
  • Resolved: 2015-08-26
Related Reports
Duplicate :  
JDK-8047212 - runtime/ParallelClassLoading/bootstrap/random/inner-complex assert(ObjectSynchronizer::verify_objmon_isinpool(inf)) failed: monitor is invalid
Relates :  
JDK-8047212 - runtime/ParallelClassLoading/bootstrap/random/inner-complex assert(ObjectSynchronizer::verify_objmon_isinpool(inf)) failed: monitor is invalid
Description
gc/lock/jni/jnilock002 failed with an assert in the GC nightlies.

#  Internal Error (/opt/jprt/T/P1/170716.jesper/s/hotspot/src/share/vm/runtime/synchronizer.cpp:1184), pid=11673, tid=139689563440896
#  assert(ObjectSynchronizer::verify_objmon_isinpool(inf)) failed: monitor is invalid

Top of stack:
V  [libjvm.so+0x107d4c1]  VMError::report_and_die()+0x151;;  VMError::report_and_die()+0x151
V  [libjvm.so+0x73dc3b]  report_vm_error(char const*, int, char const*, char const*)+0x7b;;  report_vm_error(char const*, int, char const*, char const*)+0x7b
V  [libjvm.so+0xfa562c]  ObjectSynchronizer::inflate(Thread*, oop)+0x85c;;  ObjectSynchronizer::inflate(Thread*, oop)+0x85c
V  [libjvm.so+0xfa8508]  ObjectSynchronizer::fast_enter(Handle, BasicLock*, bool, Thread*)+0x1c8;;  ObjectSynchronizer::fast_enter(Handle, BasicLock*, bool, Thread*)+0x1c8
V  [libjvm.so+0x9dcfc8]  InterpreterRuntime::monitorenter(JavaThread*, BasicObjectLock*)+0x1c8;;  InterpreterRuntime::monitorenter(JavaThread*, BasicObjectLock*)+0x1c8
j  java.util.Vector.elementAt(I)Ljava/lang/Object;+0
Comments
Copied the entries for gc/lock/jni/jnilock002 and nsk/stress/network/network004 to JDK-8047212 and verified that Aurora now associates JDK-8047212 with those failure. Closing this bug as a duplicate of JDK-8047212.
26-08-2015
Moving this bug over to runtime. It can probably be closed as a duplicate of https://bugs.openjdk.java.net/browse/JDK-8047212 as Dima suggests, but you can probably better decide if that is the correct thing to do.
15-01-2015
The symptoms are the same as in JDK-8047212 should we close it as duplicate?
12-01-2015
ILW = high (crash), low (one occurrence of this assert with this test over the last year), high (no workaround) -> p2. Nightly failure adjustment: none needed, impact & workaround already at high.
06-01-2015