This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Build: NetBeans IDE Dev (Build 201208160001) VM: Java HotSpot(TM) Client VM, 23.2-b09, Java(TM) SE Runtime Environment, 1.7.0_06-b24 OS: Windows XP User Comments: bht: running JUnit test from editor context bht: Starting a junit test suite after a project clean and build while classpath scanning was in progress. 100% CPU for the entire time. I have some doubts that it would have taken so long for the classpath scanning to complete if I had waited. bht: Starting junit test Maximum slowness yet reported was 181360 ms, average is 76792
Created attachment 123284 [details] nps snapshot
almost all the time the AWT is waiting for lock held by editor parsing loop which is computing hints. most of the time is spent in java.util.BitSet.or() 22,193 ms (52.9%) java.io.WinNTFileSystem.canonicalize0[native]() 5,489 ms (13.1%) java.io.WinNTFileSystem.canonicalizeWithPrefix0[native]() 3,982 ms (9.5%) the fs is maybe little slow but should this block awt at all?
I have greatly improved the cancellability of hints computation: http://hg.netbeans.org/jet-main/rev/90c94104a67a
Integrated into 'main-golden', will be available in build *201211200002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/90c94104a67a User: Jan Lahoda <jlahoda@netbeans.org> Log: #217065: improving cancelability of java.hints computation