JDK-6229122 : -4% SwingMark regression in b15
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2005-02-14
  • Updated: 2013-11-01
  • Resolved: 2005-04-30
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 b35Fixed
Related Reports
Relates :  
JDK-6250714 - AwtObject::scheduleDelete() doesn't work upon app shutdown
Relates :  
JDK-5065001 - awt TextArea crashes HotSpot on winXP when frame is closed
Relates :  
JDK-6259348 - PIT: ZOrder testcase resulting in VM crash
Relates :  
JDK-6480378 - Backport 5065001, 6259348 and others to 5.0 update release
Description
See Comments.
###@###.### 2005-2-14 23:40:15 GMT
Comments
EVALUATION Windows fixes integrated: Fixed 5066958: COMPATIBILITY: babel.altavista- Keyboard Translator applet- StackOverflowError Fixed 5089312: All undecorated toplevels should have zero insets, be it Frame or Dialog or Window. Fixed 6193715: Regression: AWT/NonFocusableTest and AWT/bat crashed Virtual Machine on Windows platforms) Fixed 5065001: awt TextArea crashes HotSpot on winXP when frame is closed Most likely candidate is 5065001 - we replaced a huge number of direct method calls on C++ objects (and Win32 API) with InvokeFunction, which is synchronous call to Toolkit thread. The fix allows to address a big number of crashes (potential or reproducible), so the fix is valid and necessary. However, in some cases synchronous calls can be replaced with asynchronous (when the result, explicit and implicit, is not important). ###@###.### 2005-2-15 12:12:32 GMT The problem seems to be in switching to another (toolkit) thread to run all the code, that needs to be synchronized. Another way to synchronize the access to AWT native windows objects is to introduce a dedicated critical section and use it to run the code on user threads. This would keep the synchronization and doesn't require to switch to another thread. ###@###.### 2005-04-21 11:33:31 GMT
15-02-2005