JDK-6780143 : hs203t003 hits SIGSEGV/EXCEPTION_ACCESS_VIOLATION with -XX:+UseCompressedOops
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: hs14
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-12-03
  • Updated: 2012-10-01
  • Resolved: 2011-03-08
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
6u25Fixed 7Fixed hs20Fixed
Description
Another interesting entry from my nightly analysis report:

New nsk.jvmti failures (from 2008.08.06)
    nsk/jvmti/scenarios/hotswap/HS203/hs203t003
        This test failed due to SIGSEGV on Solaris AMD64 Server VM
        (machine vm-v20z-6) and due to EXCEPTION_ACCESS_VIOLATION on
        Win-AMD64 Server VM (machine intelsdv14). This test is covered
        by the following bug:

            6545967 4/4 sp05t003 failed ResumeThread() due to
                        THREAD_NOT_SUSPENDED

        However, the bug describes a different failure mode.

        Update: I think this new crash mode only occurs with AMD64
            and the -XX:+UseCompressedOops option.

        Last failure on 2008.11.28 with Solaris AMD64 Server VM (machine vm-v20z-12) and Win-AMD64 Server VM (machine intelsdv14)
        Previous failure on 2008.11.26 with Solaris AMD64 Server VM (machine colfax002) and Win-AMD64 Server VM (machine vm-x2200-02)
Comments
EVALUATION http://hg.openjdk.java.net/jdk7/build/hotspot/rev/0fc262af204f
25-12-2010
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/0fc262af204f
10-12-2010
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/0fc262af204f
09-12-2010
EVALUATION Better summary: Summary: Using r12 as temporary register around call_VM trashes heapbase becausecall_VM doesn't always return immediately to following code (eg forward_exception, popframe and early return support).
30-11-2010
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/0fc262af204f
30-11-2010
EVALUATION Summary: missing reinit_heapbase() when popframe support jumps back into interpreter from C code.
18-11-2010