JavaFX 13 Webview hangs

[Lior Yaffe]

I figured that the problem with OpenJFX 15ea was that the webview moved to state FAILED because I was using Https with a self signed SSL certificate for the webview URL.
This worked fine in previous versions but fails in 15ea - so maybe a bug if its not intentional.
I couldn't find a nice way to print the exception from the code so I'm adding a screen capture from the debugger.
If you can show me how to access the exception from inside a StateListener I can print the stack trace nicely for you.

So I switched to Http and was able to run webview and so far it seems that 15ea indeed solves my original lockup problem.

> ----------------------------------------
> From: Guru <guru.hb at oracle.com>
> Sent: Thu Feb 13 04:47:52 CET 2020
> To: Lior Yaffe <lior.yaffe at jelurida.com>
> Cc: <openjfx-dev at openjdk.java.net>
> Subject: Re: JavaFX 13 Webview hangs
> 
> 
> Hi Lior,
> 
> Could you share a simplified test application with the html content or web content which leads to “webview frame comes up empty” so that I can test and debug at my end.
> 
> Thanks,
> Guru
> 
> > On 11-Feb-2020, at 8:51 PM, Lior Yaffe <lior.yaffe at jelurida.com> wrote:
> > 
> > Test results:
> > OpenJFX 11 never hangs
> > OpenJFX 13 always hangs
> > OpenJFX 15ea the webview frame comes up empty but the runtime never hangs
> > 
> > The Java version has no effect.
> > The hang seems to occur in native code since there is no way to take a thread dump using jstack and the only possible action is to kill the process.
> > Is there any other logging or diagnostic you can suggest? 
> >  
> > 
> > February 10, 2020 7:24:54 PM CET Kevin Rushforth <kevin.rushforth at oracle.com> wrote:    Can you also try JDK 11 with OpenJFX 13? I suspect it will not make    a difference (i.e., it will still hang), but it would be good to    confirm. And even more interesting will be the results of JavaFX    15-ea.
> > 
> >    Thanks.
> > 
> >    -- Kevin
> > 
> > On 2/10/2020 10:17 AM, Lior Yaffe      wrote:
> > 
> > The problem does not reproduce when using JavaFX        11 regardless of the version of Java being used.        
> > I will try with Java 15ea
> > 
> > On Mon, Feb 10, 2020, 17:01          Kevin Rushforth <kevin.rushforth at oracle.com>          wrote:
> > 
> >        And one last          thing to try: can you run it with the JavaFX 15-ea+1 build 
> >          and see if that makes a difference?
> > 
> >          -- Kevin
> > 
> >          On 2/10/2020 6:59 AM, Kevin Rushforth wrote:
> >> Seems I missed your comment about it being hung to the          point you can't 
> >> run jstack.
> >> 
> >> If you are using JDK 12 or later, you might try with JDK          11 and see if 
> >> that makes a difference. It will help narrow it down to a          change in 
> >> the JDK versus a change in JavaFX (although I suspect          it's a change in 
> >> JavaFX).
> >> 
> >> -- Kevin
> >> 
> >> On 2/10/2020 6:40 AM, Kevin Rushforth wrote:
> >>> A thread stack dump using "jstack" might be helpful.
> >>> 
> >>> Also, what version of the JDK are you running?
> >>> 
> >>> -- Kevin
> >>> 
> >>> 
> >>> On 2/9/2020 4:07 AM, Lior Yaffe wrote:
> >>>> My application is a Java application running a          Javascript/Html website
> >>>> inside a JavaFX WebView. It was working stable          for several years with
> >>>> various versions of Java and JavaFX.
> >>>> As far as I can tell it is following best coding          practices such as 
> >>>> running
> >>>> all UI code in the JavaFX thread and as such.
> >>>> 
> >>>> Since upgrading to JavaFX 13 my application hangs          sporadically. When it
> >>>> happens the website running inside the webview          becomes unresponsive and
> >>>> displays an hourglass icon.
> >>>> When the app hangs I cannot take a thread dump          using jstack or close 
> >>>> the
> >>>> application. I have to kill it.
> >>>> 
> >>>> The problem is reproduced on multiple Windows          workstations. It was 
> >>>> never
> >>>> reported or reproduced on Linux or Mac so there          is a chance it is 
> >>>> Windows
> >>>> specific.
> >>>> When the app hangs the CPU is ideal so this is          not a busy loop.
> >>>> Which diagnostic information can I obtain to          better understand this 
> >>>> problem?
> >>> 
> >> 
>