JDK-6833129 : specjvm98 fails with NullPointerException in the compiler with -XX:DeoptimizeALot
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 7
  • Priority: P5
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: x86
  • Submitted: 2009-04-22
  • Updated: 2010-04-02
  • Resolved: 2010-01-15
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
6u18Fixed 7Fixed hs16Fixed
Related Reports
Relates :  
JDK-6889869 - assert(!Interpreter::bytecode_should_reexecute(code),"should not reexecute")
Relates :  
JDK-6589834 - deoptimization problem with -XX:+DeoptimizeALot
Relates :  
JDK-6840775 - Multiple JVM crashes seen with 1.6.0_10 through early access of 1.6.0_14 - possibly related to GC
Description
This is split out from CR 6589834. The failure occurs on 32-bit vm on x86 platforms.
The following comments is from CR 6589834 description.

>With the internal testing option -XX:+DeoptimizeALot, running the SPECJVM98
>test _213_javac fails with NullPointerException.  While this started occurring
>with the 20070413103655.jrose.dolphin-intrinsics putback, it is actually an
>existing incompatibility between the deoptimization support and the intrinsic
>inlining of the server compiler.

The failures are intermittent, and appear in tests other than _213_javac in specjvm98
as well. -XX:-InlineArrayCopy could be used to suppress the failures.
Comments
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/9987d9d5eb0e
10-08-2009
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/9987d9d5eb0e
01-08-2009
EVALUATION See comments for details. We will have to re-execute the clone or copyOf invoke instruction rather than continue.
30-06-2009