JDK-8114203 : JVM crash while loading a wide set of fxml files
  • Type: Bug
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: fx2.0
  • Priority: P3
  • Status: Closed
  • Resolution: Incomplete
  • Submitted: 2011-07-19
  • Updated: 2015-06-16
  • Resolved: 2011-07-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
fx2.0Resolved
Related Reports
Duplicate :  
JDK-8112586 - Java crash due to invalid memory location using libjavafx-font.jnilib plugin
Relates :  
JDK-8113776 - FXMLLoader.load may fail thanks an NPE from Text.setFont
Description
I get this JVM crash at each time on Windows.
Tried Java 6 U14 and U26.
The context is a test loading plenty of fxml files, one after the other, doing a renderingToImage and comparison against reference.
Before the crash I get several exceptions as described in the RT-14955 (NPE); I dunno if the JVM comes to a state the next NPE kills it or if root cause is completely separated from what is described in RT-14955.
What is sure however is that the crash occurs only if you run the test on the whole set of fxml files: if you run it only against the fxml file which is processed at crash time then it goes perfectly well.

     [java] #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x72720c9a, pid=3552, tid=2884
     [java] #
     [java] # JRE version: 6.0_26-b03
     [java] # Java VM: Java HotSpot(TM) Client VM (20.1-b02 mixed mode windows-x86 )
     [java] # Problematic frame:
     [java] # C  [javafx-font.dll+0x30c9a]
Comments
The Java portion of the stack trace shows that we are retrieving a glyph outline. The native portion shows we are in a JNI call that isn't used in that case, so it appears bogus. RT-12684 looks close in that its also related to retrieving outlines but it is apparently only related to OTF/CFF fonts and there aren't any of those on Windows. I need some kind of test case for this bug in order to do anything. Marking incomplete pending that.
25-07-2011
This looks like a possible duplicate of RT-12684
21-07-2011
Hi Kevin, This looks like it could be a native font issue. Not sure who it should go to. Greg
19-07-2011