JDK-8020038 : [macosx] Incorrect usage of invokeLater() and likes in callbacks called via JNI from AppKit thread
- Type: Bug
- Component: client-libs
- Sub-Component: java.awt
- Affected Version: 7u25,7u40,8
- Priority: P2
- Status: Closed
- Resolution: Fixed
- OS: os_x
- Submitted: 2013-07-08
- Updated: 2014-10-15
- Resolved: 2013-07-11
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.
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 7 | JDK 8 |
|---|---|
7u40Fixed  |
8 b100Fixed |
Related Reports
|
Duplicate :
|
Description
There is a number of cases where a Java callback called via JNI from AppKit thread uses invokeLater() and likes to run a code that notifies listeners/modifies UI state, which leads to all kinds of problems, like user code being called in incorrect thread group or deadlocks.
Comments
|