-
Bug
-
Resolution: Fixed
-
P4
-
8
-
None
-
b58
-
generic
-
generic
-
Verified
In order to optimize and clarify lock sequence in EventQueue & PostEventQueue the following steps should be done:
1. Remove flushLock from SunToolkit.flushPendingEvent()
1a. Try to remove SunToolkitSubclass (if possible)
2. Return method PostEventQueue.flush() as 'synchronized' back
3. Add call of SunToolkit.flushPendingEvents() to EventQueue.detachDispatchThread(),
right before pushPopLock.lock()
4. Remove !SunToolkit.isPostEventQueueEmpty() check from EventQueue.detachDispatchThread()
5. Remove SunToolkit.isPostEventQueueEmpty() & PostEventQueue.noEvents();
Run tests mentioned in CR 4648733
1. Remove flushLock from SunToolkit.flushPendingEvent()
1a. Try to remove SunToolkitSubclass (if possible)
2. Return method PostEventQueue.flush() as 'synchronized' back
3. Add call of SunToolkit.flushPendingEvents() to EventQueue.detachDispatchThread(),
right before pushPopLock.lock()
4. Remove !SunToolkit.isPostEventQueueEmpty() check from EventQueue.detachDispatchThread()
5. Remove SunToolkit.isPostEventQueueEmpty() & PostEventQueue.noEvents();
Run tests mentioned in CR 4648733
- relates to
-
-
- Closed
-
-
JDK-7188708 REGRESSION: closed/java/awt/EventQueue/PostEventOrderingTest.java fails
-
- Closed
-
-
-
- Closed
-
-
JDK-2226952 Deadlock between PostEventQueue.noEvents, EventQueue.isDispatchThread and SwingUtilities.invokeLater
-
- Closed
-