JDK-6259348 : PIT: ZOrder testcase resulting in VM crash
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 5.0u7,6
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows,windows_xp
  • CPU: x86
  • Submitted: 2005-04-21
  • Updated: 2011-01-19
  • Resolved: 2005-07-23
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
6 b45Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
This occurs only with b35 AWT PIT build. 

java -version
java version "1.6.0-awt.pit-int-jcg-win-03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-awt.pit-int-jcg-win-03-java2d_19_apr_2005_08_17)
Java HotSpot(TM) Client VM (build 1.6.0-ea-b32, mixed mode)

Running the attached automated testcase results in VM crash on WinXP system. The testcase runs fine on b32. Run the testcase as:

java -DresultsDir=. setZOrderContainerTest5

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00abc751, pid=1520, tid=2028
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0-ea-b32 mixed mode)
# Problematic frame:
# CFocusLost: java.awt.FocusEvent[FOCUS_LOST,temporary,opposite=null,cause=ACTIV
ATION] on java.awt.Button[button1,5,5,59x23,label=Button 5]
  0x00abc751
#
# An error report file with more information is saved as hs_err_pid1520.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

Attached is the crash log.

###@###.### 2005-04-21 13:28:37 GMT

Comments
EVALUATION The crash always happens while the application is shutdowning. The problem is in destroying native AWT objects: we try to delete a component simultaneously from two different placed. In the fix for 6229122 I tried to synchronize deleting native objects and all other actions, but this particular case hadn't been covered: if we get WmDestroy while cleaning up AwtObjectList (the list that contains all the native AWT objects), we get a crash. I need to check if the same problem causes some other recent crashes, like 6268999. ###@###.### 2005-05-14 15:14:35 GMT
14-05-2005

SUGGESTED FIX Synchronize deleting native object from WmDestroy and all other AwtToolkit::SyncCall routines (including cleaning up theAwtObjectList). ###@###.### 2005-05-14 15:14:35 GMT
14-05-2005