- 
    Bug 
- 
    Resolution: Fixed
- 
     P2 P2
- 
    7u25, 7u40, 8
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8020904 | 7u60 | Leonid Romanov | P2 | Resolved | Fixed | b01 | 
| JDK-8021105 | 7u45 | Leonid Romanov | P2 | Closed | Fixed | b04 | 
| JDK-8020590 | 7u40 | Leonid Romanov | P2 | Closed | Fixed | b34 | 
                    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. 
            
- backported by
- 
                    JDK-8020904 [macosx] Incorrect usage of invokeLater() and likes in callbacks called via JNI from AppKit thread -           
- Resolved
 
-         
- 
                    JDK-8020590 [macosx] Incorrect usage of invokeLater() and likes in callbacks called via JNI from AppKit thread -           
- Closed
 
-         
- 
                    JDK-8021105 [macosx] Incorrect usage of invokeLater() and likes in callbacks called via JNI from AppKit thread -           
- Closed
 
-         
- duplicates
- 
                    JDK-8017334 [macosx] jxBrowser demo locks up in 7u25 -           
- Closed
 
-