Build: NetBeans IDE 6.8 Beta (Build 200910212001)
VM: Java HotSpot(TM) Client VM, 11.3-b02, Java(TM) SE Runtime Environment, 1.6.0_13-b03
OS: Windows Vista
GUEST: rodando fx
Maximum slowness yet reported was 3122 ms, average is 3122
Created attachment 94042 [details]
From the snapshot it was the first execution of the JavaFX application after start and the execution was blocked for 1130ms by org.openide.filesystems.URLMapper just to obtain URL.
But URLMapper is not the reason, I see there Lucene Merge Thread consuming 2930ms CPU time and many other threads waiting exactly the same amount of time on locks.
I don't know who owns the Lucene module so please re-assign to the right person, thanks.
The issues is about blocking AWT event queue (slowness detector issue), other threads are not relevant.
Anyway feel free to decrease the priority, I personally think that the issue is not important at all.
full snapshot time is 2930ms and during the whole time was one CPU core saturated with Lucene Merge Thread.
JavaFX Action Provider was blocking AWT Thread for 2930ms (1515ms pure CPU time).
- 1110ms (respectively 906ms) of that time spent by initializing of org.apache.tools.ant.module.api.AntTargetExecutor
- 1130ms waiting on blocked org.openide.URLMapper
Proposed fix is to detach the JavaFX Action Provider actions from AWT thread.
Java FX v1 including Java FX Script is no longer supported.
Cleaning bugzilla categories ....