JDK-6755845 : JVM_FindClassFromBoot triggers assertions
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-10-03
  • Updated: 2012-10-08
  • Resolved: 2008-11-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7 Other
6u14Fixed 7Fixed hs14Fixed
Related Reports
Relates :  
JVM_FindClassFromBootLoader triggers assertions in debug builds.

# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc:  SuppressErrorAt=/interfaceSupport.hpp:170
# A fatal error has been detected by the Java Runtime Environment:
#  Internal Error (/net/baggy.sfbay/allmine/hg-launcher/jdk7/hotspot/src/share/vm/runtime/interfaceSupport.hpp:170), pid=9791, tid=2
#  Error: assert(thread->thread_state() == _thread_in_native,"coming from wrong thread state")
# Java VM: Java HotSpot(TM) Client VM (14.0-b05-hg-launcher.ksrini.1003-fastdebug mixed mode solaris-sparc )

EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/f008d3631bd1

EVALUATION Need to refactor the JVM_FindClassFromBootLoader and JVM_FindClassFromClassLoader corrrectly, as one JVM entry point cannot call another, as it will set the thread state incorrectly and twice.