-
Bug
-
Resolution: Fixed
-
P2
-
6
-
b07
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2143846 | 6u1 | Igor Kushnirskiy | P2 | Resolved | Fixed | b01 |
SwingWorker notifications might be out of order.
After the fix for 6449017 [SwingWorker performance is sluggish] some
of the SwingWorker notifications come by a different route than
before. While the spec does not provide any guarantees about the order
asynchronous notifications are to be handled the usual expectation is
notification which is sent later is to be handled later. After that
fix it is not the case any more. SwingWorker might receive "progress"
property change after done method is invoked for example.
After the fix for 6449017 [SwingWorker performance is sluggish] some
of the SwingWorker notifications come by a different route than
before. While the spec does not provide any guarantees about the order
asynchronous notifications are to be handled the usual expectation is
notification which is sent later is to be handled later. After that
fix it is not the case any more. SwingWorker might receive "progress"
property change after done method is invoked for example.
- backported by
-
JDK-2143846 SwingWorker notifications might be out of order.
-
- Resolved
-