JDK-6725983 : Assertion "method->method_holder())->is_not_initialized(),"method holder must be initialized"
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-07-15
  • Updated: 2011-09-22
  • Resolved: 2011-04-25
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 7 Other
7Fixed hs21Fixed
Description
Problem Description    : fastdebug JVM crashes with assertion
 #  Internal Error (/BUILD_AREA/jdk7/hotspot/src/share/vm/compiler/compileBroker.cpp:946), pid=31733, tid=3084860304
 #  Error: assert(!instanceKlass::cast(method->method_holder())->is_not_initialized(),"method holder must be initialized")

JDK Release / Build     : 6, 6u1 - 6u10, 7
Bits                    : fastdebug, both 32 and 64 bits
VM flavors              : client | server
VM Modes                : -Xmixed | -Xcomp
Java flags              :
Platform(s)             : all
Hostnames with OS info  :
Comments
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/bc6b27fb3568
01-03-2011
EVALUATION This bug was found by Intel as part of jdk port on Itanium. If you think CompileTheWorldIgnoreInitErrors should not be used then could it be removed?
29-08-2010
EVALUATION I don't think you can safely run with -XX:+CompileTheWorldIgnoreInitErrors or you will get errors like this. You can either ignore them or don't use the flag. I'm honestly not sure why this flag exists. Why did you start using?
28-08-2010