Re: [jdk17] RFR: 8266079: Lanai: AlphaComposite shows differences on Metal compared to OpenGL [v2]

On Wed, 23 Jun 2021 12:15:03 GMT, Alexey Ushakov wrote: >> Implemented blit via compute kernel > > Alexey Ushakov has refreshed the contents of this pull request, and previous > commits have been removed. The incremental views will show differences > compared to the previous content of the PR.

Re: deadlock between AppKit main thread and AWT event thread in JDK 17

To avoid this deadlock, the run loop name is required when using the NSObject method performSelectorOnMainThread:withObject:waitUntilDone:modes: JNF calls this method with the “old” run loop

Re: deadlock between AppKit main thread and AWT event thread in JDK 17

> On Jun 28, 2021, at 9:50 AM, Alan Snyder wrote: > > To avoid this deadlock, the run loop name is required when using the NSObject > method performSelectorOnMainThread:withObject:waitUntilDone:modes: >

Re: deadlock between AppKit main thread and AWT event thread in JDK 17

My code (#2) running on the AWT thread is blocked trying to perform selector on main thread waiting YES. It is blocked because it does not specify that it can be run under the javaRunLoopMode. It specifies the AWTRunLoopMode, which is the old name. That name is supplied by JavaNativeFoundation.

Re: deadlock between AppKit main thread and AWT event thread in JDK 17

> On Jun 28, 2021, at 9:30 AM, Alan Snyder wrote: > > My code (#2) running on the AWT thread is blocked trying to perform selector > on main thread waiting YES. It is blocked because it does not specify that it > can be run under the javaRunLoopMode. It specifies the AWTRunLoopMode, which

Re: deadlock between AppKit main thread and AWT event thread in JDK 17

> On Jun 28, 2021, at 9:03 AM, Alan Snyder wrote: > > You can call performSelectorOnMainThread directly, but you have to know the > name of the AWT/Java run loop to avoid the deadlock situations that I have > encountered. > > The name of the run loop needs to be part of the public API. I

Re: deadlock between AppKit main thread and AWT event thread in JDK 17

You can call performSelectorOnMainThread directly, but you have to know the name of the AWT/Java run loop to avoid the deadlock situations that I have encountered. The name of the run loop needs to be part of the public API. By the way, upcalls from AppKit to get accessibility information has

Re: deadlock between AppKit main thread and AWT event thread in JDK 17

> On Jun 28, 2021, at 7:51 AM, Alan Snyder wrote: > > Hmm… it appears that in removing JavaNativeFoundation from the JDK the name > of the run loop was changed from AWTRunLoopMode to javaRunLoopMode. > > If that is correct, it is an incompatible change that breaks third party use > of

Re: deadlock between AppKit main thread and AWT event thread in JDK 17

Hmm… it appears that in removing JavaNativeFoundation from the JDK the name of the run loop was changed from AWTRunLoopMode to javaRunLoopMode. If that is correct, it is an incompatible change that breaks third party use of JavaNativeFoundation for running code on the main thread. It also