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.
This bug was originally marked as duplicate of bug 242818, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE 8.0.1 (Build 201408251540) VM: Java HotSpot(TM) 64-Bit Server VM, 25.0-b70, Java(TM) SE Runtime Environment, 1.8.0-b132 OS: Windows 7 User Comments: iluvtr: Slow NB when compiling Maximum slowness yet reported was 24064 ms, average is 24064
Created attachment 149503 [details] nps snapshot
Mostly slow I/O while classloading. Not much to do with it: http://statistics.netbeans.org/exceptions/exception.do?id=748333 the only thing that comes to my mind is to pre-load the org.netbeans.modules.bugtracking.api.Util.getIssueSpans() code on background when the editor opens.
> Mostly slow I/O while classloading. Not much to do with it: > http://statistics.netbeans.org/exceptions/exception.do?id=748333 > the only thing that comes to my mind is to pre-load the > org.netbeans.modules.bugtracking.api.Util.getIssueSpans() > code on background when the editor opens. org.netbeans.modules.bugtracking.api.Util.getIssueSpans() is triggered by java.awt.AWTEventMulticaster.keyPressed() preloading doesn't help much as the result should be based on actual editor data also that bugtracking wasn't supposed to initialize until not necessary. This would now happen on first file open. not much bugtracking could do against slow classloading either possible workaround: - in case you have and use bugtracking repositories keep the Tasks view open. It triggers BT initialization and therefore prevents a potentially slow response on a later file open - in case you have bugtracking repositories but do not need them, then removing them should help.
*** Bug 254175 has been marked as a duplicate of this bug. ***