To reproduce the bug, run the attached test and just move the slider. When the slider is more than half, you will get OOME in the command prompt.

Here is the stack trace -
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.javafx.runtime.provider.GUIRuntimeProvider.run(GUIRuntimeProvider.java:68)
at com.sun.javafx.runtime.Entry.start(Entry.java:84)
at com.sun.javafx.runtime.Main.main(Main.java:80)

Caused by: java.lang.OutOfMemoryError: Java heap space
at com.sun.saffron.ADFImplicitFloat.SetGlyphInterior(ADFImplicitFloat.java:2477)
at com.sun.saffron.ADFImplicitFloat.ADFRenderGlyphImplicit(ADFImplicitFloat.java:3295)
at com.sun.saffron.ADFImplicit.ADFRenderGlyphImplicit(ADFImplicit.java:13)
at com.sun.prism.impl.ps.ShapeUtil.getMaskData(ShapeUtil.java:121)
at com.sun.prism.impl.ps.BaseShaderGraphics.fillShape(BaseShaderGraphics.java:113)
at com.sun.prism.impl.BaseGraphics.draw(BaseGraphics.java:184)
at com.sun.javafx.sg.prism.NGText.renderContent(NGText.java:50)
at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:255)
at com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:101)
at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:255)
at com.sun.javafx.tk.prism.PrismScene$1.run(PrismScene.java:230)
at com.sun.prism.tk.RunnableEvent.run(RunnableEvent.java:47)
at com.sun.prism.tk.PrismToolkitImpl.processRenderEvent(PrismToolkitImpl.java:157)
at com.sun.prism.tk.PrismToolkitImpl.processRenderTasks(PrismToolkitImpl.java:173)
at com.sun.prism.tk.PrismToolkitImpl.run(PrismToolkitImpl.java:109)
at com.sun.javafx.tk.prism.PrismToolkit.startup(PrismToolkit.fx:126)

I reproduced it on WinXP-x64 - soma-graphics-scrum-b142 - 6u14. Not reproducible on Swing pipeline.