Ways to activate debug log on JavaFX 8 / support for bug reports ?

Question

Hello,
Since, there is to much time until next march, I've downloaded the JDK8 u 87 and started to play with JavaFX 8. Very nice things, but I am going into a lot of obscure bugs
* For example, when closing an application that does only CSS styling I keep getting this exception when closing the window:
java.lang.NullPointerException
     at com.sun.glass.ui.View.notifyRenderingEnd(View.java:352)
     at com.sun.javafx.tk.quantum.PaintCollector.done(PaintCollector.java:308)
     at com.sun.prism.render.RenderJob.run(RenderJob.java:75)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
     at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:129)
     at java.lang.Thread.run(Thread.java:724)
This happens 15% of the time. The same story ( but different exception ) for a simple application for playing with sliders.
I would open some bugs but 2 things come to my mind:
* are there any ways to activate debug log so that developers see a bit more that just a stack trace?
* I saw on JavaFX 2 jira that you can't attach files to an issue, so basically how can I report stuff that prove things if I can't attach any file?
Regards,
subzero
Edited by: subzero on May 1, 2013 5:50 AM
Edited by: subzero on May 1, 2013 5:51 AM

Answer 1

subzero wrote:
java.lang.NullPointerException
     at com.sun.glass.ui.View.notifyRenderingEnd(View.java:352)
     at com.sun.javafx.tk.quantum.PaintCollector.done(PaintCollector.java:308)
     at com.sun.prism.render.RenderJob.run(RenderJob.java:75)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
     at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:129)
     at java.lang.Thread.run(Thread.java:724)This particular exception is described in RT-30014 and has already been fixed:
https://javafx-jira.kenai.com/browse/RT-30014
Artem