I think I ran into this a bit when I had a mixed swing/javafx application. It was always due to inadvertently performing Swing activity while still in the JFX thread or visa versa. I think sometimes checking the stack frame on both threads would show me where it was (but sometimes not). I think I was always able to solve it with the right SwingUtilities.invokeLater() or Platform.runLater().
My apologies if you already knew all this (and for the fact that it wasn’t really helpful). I’ve heard mention on this list that there is a new “single event thread” setting for JFX 8. I’ve wondered if that would have magically solved this issue, and allowed one to remove the runLater() calls. jeff On May 13, 2015, at 9:04 AM, Pedro Duque Vieira <pedro.duquevie...@gmail.com> wrote: > Anyone...? (see below) > > On Mon, May 11, 2015 at 8:03 PM, Pedro Duque Vieira < > pedro.duquevie...@gmail.com> wrote: > >> >> Hi, >> >> >> >> Already posted this on the OTN forum but got no response. >> >> >> I have a swing/javafx app that is hanging randomly without any error >> information (exceptions thrown, etc). I run the app with the pulse logger >> flag active and when it hangs the pulse logger stops. >> >> >> >> How can I debug this? What can cause the pulse logger to stop? Is this my >> fault or some javafx bug? >> >> >> Thanks, best regards, >> -- >> Pedro Duque Vieira >> > > > > -- > Pedro Duque Vieira
