JDK-4309720 : HS2.0: accessed idom for root while processing loops
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 2.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_nt
  • CPU: x86
  • Submitted: 2000-02-03
  • Updated: 2000-02-17
  • Resolved: 2000-02-17
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
2.0 fcsFixed
Related Reports
Relates :  
JDK-4308797 - the concurrently executed threads crash the HotSpot 2.0merlin on Win32
Relates :  
JDK-4287571 - c2-100299 assert in synchronizer.cpp 176 in comp+verifybeforegc
Description
HotSpot 2.0-rc2A (win32) crashes while trying to execute the JCK-stress test
jck12a003: when executed in -Xcomp mode under WinNT 4.0, java_g.exe terminates 
with the following diagnostics: 
    #
    # HotSpot Virtual Machine Error, assertion failure
    #
    # assert(test != 0, "Unexpected object header as 0!")
    #
    # Error ID: C:\hotspot2\src\share\vm\runtime\synchronizer.cpp, 176
    #
    # Problematic Thread: prio=5 tid=0xf927eb8 nid=0x12b runnable
    #

This crash looks like a regression of the bug #4287571

Note also, that java.exe intermittently terminates with the following 
diagnostics (while trying to execute jck12a003): 
    #
    # HotSpot Virtual Machine Error, EXCEPTION_ACCESS_VIOLATION
    #
    # Error ID: 4F533F57494E13120E43505002D9
    #
    # Problematic Thread: prio=5 tid=0x2f590940 nid=0x328 runnable 
    #
(ErrorID == "os_win32.cpp, 729")

This kind of crash looks the same as the HS crash described by #4308797 

The test /nsk/stress/jck12a/jck12a003 belongs to the testbase located 
in the directory /net/sqesvr/vsn/testbase/testbase_nsk 

To reproduce this bug, please try the script 'doit.bat' in the 
directory /net/sqesvr/vsn/GammaBase/Bugs/<this_bug_number>
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: 2.0_fcs INTEGRATED IN: 2.0_fcs
14-06-2004
EVALUATION michael.paleczny@eng 2000-02-07 Reported problem was not observed. Reproduced a problem while compiling method 'run' in loop optimizer. michael.paleczny@eng 2000-02-11 After fix for KeyFire, on K7-750, hit assert(ObjectSynchronizer::verify_objmon_isinpool(mark->monitor()), "monitor is invalid"); michael.paleczny@eng 2000-02-15 Retested with current build. Application hangs; thread dump using -XX:+DumpVMLocks option indicates this is an application error.
15-02-2000