Freeze when double click entry to edit entry 5.0DEV

JabRef version jdk1.8.0_172
on Mac OS Mojave 10.14

• [-] I have tested the latest development version from http://builds.jabref.org/master/ and the problem persists.

Steps to reproduce the behavior:

1. Run the command line to open JabRef (.bib file has 200 entries)
2. Double click one entry to open "edit entry" window
3. Then JabRef has frozen for about 60 seconds, and nothing shows.
4. Double click the same entry again, the "edit entry" window shows immediately.
5. Click any tab in the "edit entry" window, it freezes too.
6. When the "edit entry" window is shown, click other entry to change an entry, it freezes too.

I ran the JabRef with the following command:
/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/bin/java -jar JabRef--master--latest.jar
and got the following log:

Log File

15:57:45.527 [JavaFX Application Thread] INFO  org.jabref.logic.importer.OpenDatabase - Opening: /*******/***.bib
2018-11-05 15:58:17.362 java[4420:60895] unrecognized type is 4294967295
2018-11-05 15:58:17.362 java[4420:60895] *** Assertion failure in -[NSEvent _initWithCGEvent:eventRef:], /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1671/AppKit.subproj/NSEvent.m:1969
2018-11-05 15:59:15.337 java[4420:60895] unrecognized type is 4294967295
2018-11-05 15:59:15.337 java[4420:60895] *** Assertion failure in -[NSEvent _initWithCGEvent:eventRef:], /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1671/AppKit.subproj/NSEvent.m:1969
2018-11-05 15:59:42.130 java[4420:60895] unrecognized type is 4294967295
2018-11-05 15:59:42.130 java[4420:60895] *** Assertion failure in -[NSEvent _initWithCGEvent:eventRef:], /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1671/AppKit.subproj/NSEvent.m:1969
.....

[Siedlerchr]

Thanks for your report, unfortunately it seems to be some java bug itself where we can't do anything about at the moment, I fear:
https://bugs.openjdk.java.net/browse/JDK-8211304

Thanks for your report, unfortunately it seems to be some java bug itself where we can't do anything about at the moment, I fear:
https://bugs.openjdk.java.net/browse/JDK-8211304

Thanks for the useful information.