JDK-6450320 : jvmpi causes a hang in 5.0u7
  • Type: Bug
  • Component: vm-legacy
  • Sub-Component: jvmpi
  • Affected Version: 5.0u7
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: linux
  • CPU: x86
  • Submitted: 2006-07-19
  • Updated: 2014-02-27
  • Resolved: 2007-06-29
Related Reports
Relates :  
JDK-6186200 - RFE: Stall allocation requests while heap is full and GC locker is held
Description
When the attached program(bid6266681.c/bid6266681.java) is executed in 5.0, a hang will occurs.

The following is the trace information with gdb.

(gdb) where
#0  0xb75d227d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0
#1  0xb75d27cd in pthread_cond_wait@GLIBC_2.0 () from /lib/tls/libpthread.so.0
#2  0xb6f7bf8e in os::Linux::safe_cond_wait ()
   from /JavaL3/users/ooooo/java-bin/jdk1.5.0_07/jre/lib/i386/client/libjvm.so
#3  0xb6f683b4 in Monitor::wait ()
   from /JavaL3/users/ooooo/java-bin/jdk1.5.0_07/jre/lib/i386/client/libjvm.so
#4  0xb6e31c9d in GC_locker::stall_until_clear ()
   from /JavaL3/users/ooooo/java-bin/jdk1.5.0_07/jre/lib/i386/client/libjvm.so
#5  0xb6df2529 in TwoGenerationCollectorPolicy::mem_allocate_work ()
   from /JavaL3/users/ooooo/java-bin/jdk1.5.0_07/jre/lib/i386/client/libjvm.so
#6  0xb6e3551d in GenCollectedHeap::mem_allocate ()
   from /JavaL3/users/ooooo/java-bin/jdk1.5.0_07/jre/lib/i386/client/libjvm.so
#7  0xb6d2a038 in CollectedHeap::common_mem_allocate_noinit ()
   from /JavaL3/users/ooooo/java-bin/jdk1.5.0_07/jre/lib/i386/client/libjvm.so
#8  0xb6e4cb17 in instanceKlass::allocate_instance ()
   from /JavaL3/users/ooooo/java-bin/jdk1.5.0_07/jre/lib/i386/client/libjvm.so
#9  0xb6db08ae in Runtime1::new_instance ()
   from /JavaL3/users/ooooo/java-bin/jdk1.5.0_07/jre/lib/i386/client/libjvm.so


NOTE:
 The attached program tries to do
  1) One thread tries to allocate repeatedly.(GC will occurs periodically)
  2) Another thread tries to lock/unlock thru jvmpi
Comments
EVALUATION JVMPI is the old (and experimental) profiling interface. It was never part of the platform specification and was deprecated in J2SE 5.0. Its replacement is the JSR-163 specified JVM Tool Interface (JVM TI) that was added in J2SE 5.0. Since 5.0 the documentation on the java.sun.com site was updated to alert developers that this interface would be removed in a future release. It was disabled in Java SE 6 and the code has been completely removed in Java SE 7. Here are some links with more information on this topic: http://java.sun.com/j2se/1.5.0/docs/guide/jvmpi/ http://java.sun.com/javase/6/webnotes/compatibility.html#incompatibilities I am closing this bug as "will not fix".
29-06-2007