Question about deadlock issue

Kevin Rushforth kevin.rushforth at oracle.com
Thu Sep 17 12:56:25 UTC 2020


Update: I cannot reproduce this even using your updated instructions. 
How often does it reproduce for you? Have you tried with a more recent 
JDK (in case it is a JDK bug)? I recommend trying it with the 
just-released JDK 15 [1].

-- Kevin

[1] https://jdk.java.net/15/


On 9/17/2020 5:26 AM, Kevin Rushforth wrote:
> If you have additional information that is relevant to reproducing the 
> bug or helpful in identifying a possible fix, you can send it to this 
> alias and either I or another OpenJFX Author, Committer, or Reviewer 
> can add it to the bug report. I have updated the bug report with your 
> note about where you found the situation reproducible.
>
> Since the bug is easily reproducible with no known workaround, I set 
> the target fix version to JavaFX 16, but there are no guarantees. If 
> you or another developer want to take a stab at contributing a fix, 
> that would make it more likely to be fixed sooner.
>
> -- Kevin
>
>
> On 9/17/2020 4:01 AM, Steven Yi wrote:
>> Hi All,
>>
>> I had reported a deadlock issue that requires app restart whenever a
>> context menu is shown in JFX embedded within Swing (i.e., JFXPanel) on
>> macOS:
>>
>> https://bugs.openjdk.java.net/browse/JDK-8251038
>>
>> I had not seen any updates on the issue in a month and I'm wondering
>> what to do. This is a serious bug for me and I'd like to have as
>> informed an opinion at this point on my decision on whether to
>> continue using JavaFX. Any advice here would be appreciated.
>>
>> A few things:
>>
>> * I wanted to add information to the ticket but I'm a 3rd party bug
>> reporter and I do not see how one can do this. I found that this
>> situation is reproducible if I use "built-in" context menus, such as
>> right clicking a text field. I thought I might be able to replace my
>> own JFX code to use Swing popups and windows where necessary, but
>> going and patching the built-in controls felt like too much.
>>
>> * I tested using the recently released JavaFX 15 and found the
>> deadlock to still be reproducible. (Using AdoptOpenJDK 11.0.8+10)
>>
>> * I don't really understand the JBS in regards to priority (i.e, what
>> P3 means).  I understand that using JavaFX within a Swing application
>> may not be a priority for anyone else but myself. However, I am trying
>> to understand if this is being looked at and if there's any way for me
>> to figure out a timeline so I can make a decision whether to remove
>> JavaFX from my application or not. There is a lot of code in my
>> application that I'd have to port back to Swing, but realizing that
>> any macOS user of my app is pretty much going to run into this at some
>> point, I have to seriously consider this option.
>>
>> Thanks,
>> Steven
>



More information about the openjfx-dev mailing list