-
Enhancement
-
Resolution: Fixed
-
P3
-
8
-
b75
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8018686 | 7u45 | Unassigned | P3 | Closed | Fixed | b01 |
JDK-8014107 | 7u40 | Unassigned | P3 | Closed | Fixed | b25 |
Right now, most, if not all, native methods in LWAWT are called on event dispatch thread or other Java threads. In native, these methods contain the threading check:
AWT_ASSERT_NOT_APPKIT_THREAD;
However, these checks are mostly unnecessary since a user application just can't access the AppKit thread managed by AWT native code. Therefore these methods are always called from non-AppKit thread just by code design. These checks only consume memory and CPU resources. Also, for experimental purposes it may be useful to call some of these methods from the AppKit thread sometimes, in which case the checks do a bad job.
AWT_ASSERT_NOT_APPKIT_THREAD;
However, these checks are mostly unnecessary since a user application just can't access the AppKit thread managed by AWT native code. Therefore these methods are always called from non-AppKit thread just by code design. These checks only consume memory and CPU resources. Also, for experimental purposes it may be useful to call some of these methods from the AppKit thread sometimes, in which case the checks do a bad job.
- backported by
-
JDK-8014107 [macosx] Make LWAWT be able to run on AppKit thread
-
- Closed
-
-
JDK-8018686 [macosx] Make LWAWT be able to run on AppKit thread
-
- Closed
-