JDK-6511174 : -XX:+AggressiveOpts option makes JVM to crash
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 5.0u6
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_10
  • CPU: sparc
  • Submitted: 2007-01-09
  • Updated: 2010-04-02
  • Resolved: 2007-01-10
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.
Other
5.0u6Resolved
Related Reports
Duplicate :  
JDK-6451451 - EXCEPTION_ACCESS_VIOLATION caused by -XX:+AggressiveOpts flag in Bigapps ATG test for 1.5.0_08b03
Description
Using -XX:+AggressiveOpts when running with WebSphere Application Server 6.1 generates the core dump.
Comments
EVALUATION EliminateZeroing elides the required zeroing of newly allocated char arrays in cases where we can prove that they will be completely overwritten immediately after creation. It normally triggers when creating new String instances. See 6337834 for a little more info.
09-01-2007
EVALUATION When ran with the following option the server started well and we did not see the same crash anymore however we need to put this into stress and make sure it is fine under stress as well: -XX:+AggressiveOpts -XX:+UnlockDiagnosticVMOptions -XX:-EliminateZeroing -XX:+PrintCommandLineFlags What is the meaning of EliminateZeroing and what will be impact on the performance ? I will take a look at the other bug in the meantime.. Thanks very much for the info.
09-01-2007
EVALUATION Isn't this a dup of 6451451? Try running with -XX:-EliminateZeroing. I thought we'd concluded this already...
09-01-2007