JDK-2172283 : Crash in sun.awt.windows.WToolkit.eventLoop()
  • Type: Backport
  • Backport of: JDK-6723941
  • Component: client-libs
  • Sub-Component: java.awt
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • Submitted: 2009-01-28
  • Updated: 2011-01-19
  • Resolved: 2009-04-22
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
6u14Fixed
Description
JDK              : JDK 1.4.2_20
Platforms[s]     : x64 - Windows Vista - jvm64
testbase         : /net/vice.russia.sun.com/export/home0/dtf/dtf_ws/suites/142_Suites/awt 

This test passed on 1.4.2_19 and fails on 1.4.2_20

Results:
http://stt-13.russia.sun.com/results/1.4.2_20/b01_j4b/awt/winvista-amd64/run1/winvista-amd64/awt_stt_suites_winvista-amd64/root.Windows_Vista.amd64/bug_4710511/

Crash Log:
http://stt-13.russia.sun.com/results/1.4.2_20/b01_j4b/awt/winvista-amd64/run1/winvista-amd64/awt_stt_suites_winvista-amd64/root.Windows_Vista.amd64/bug_4710511/hs_err_pid1444.log
Comments
EVALUATION While there was a fix for this bug, its application led to 6830549. After finding out why, I approached AWT with the problem. They informed me that these issues have already been resolved in 5u14 as part of the "big awt fix" and that backporting this to 1.4.2 would require considerable effort and engineering resources. I informed QA and received the response below. Based on that I'm closing as "will not fix" QA's response: "In summary, these issues cannot be fixed unless we backport the "big AWT fix" from 5u14. Obviously this would take a massive engineering effort. However, given the complexity and your assessment on engineering effort involved and no customer asking for it, I think, fine to close 6723941 as 'Will Not Fix' with your analysis and comments so that we know why this bug is closed if some one asks in the future."
22-04-2009
EVALUATION From the evaluation of parent CR, it's obvious that fix # 6542975 went into 6u10 is causing this regression in 6ux train. This fix # 6542975 never went into 1.4.2_xx release or 5.0ux. This failure not noticed in 5.0u18 b01 testing and also not in 1.4.2_19-rev-b07. Fixes from 1.4.2_19-rev-b07 has been synced into 1.4.2_20 b01 so fixes went alone in 1.4.2_20 b01 might cause this but at the same time the same fixes went into 5.0u18 where no failure. After testing on submitter provided machine with 1.4.2_20 b01 and 1.4.2_19-rev-b07 (4 times or more) could NOT reproduce it. Also tested on su24-01.sfbay.sun.com. machine with 1.4.2_20 b01 and 1.4.2_19-rev-b07 (4 times of more) NO failure noticed. Seems like the JDK location submitter used is corrupted or has some other stuff. Is this problem reproducible in more than one test system ? See comment section for test log.
29-01-2009