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 200908022240) VM: Java HotSpot(TM) Client VM, 14.1-b02, Java(TM) SE Runtime Environment, 1.6.0_15-b03 OS: Windows XP, 5.1, x86 User Comments: limlom: Loaded old project files and started running project Maximum slowness yet reported was 29110 ms, average is 9938
Created attachment 86276 [details] nps snapshot
Created attachment 86277 [details] nps snapshot
This issue already has 5 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=154803
Build: NetBeans IDE Dev (Build 200908022240) VM: Java HotSpot(TM) Client VM, 11.2-b01, Java(TM) SE Runtime Environment, 1.6.0_12-b04 OS: Windows Vista, 6.0, x86 User Comments: starting a webapp Maximum slowness yet reported was 32875 ms, average is 12753
Created attachment 86293 [details] nps snapshot
This issue already has 6 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=154803
Build: NetBeans IDE Dev (Build 200908022240) VM: Java HotSpot(TM) Client VM, 11.2-b01, Java(TM) SE Runtime Environment, 1.6.0_12-b04 OS: Windows Vista, 6.0, x86 User Comments: starting a webapp Maximum slowness yet reported was 95068 ms, average is 24512
Created attachment 86294 [details] nps snapshot
This issue already has 7 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=154803
This issue already has 9 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=154803
I believe Denis fixed this one.
Yes, it is already fixed. It is all about isServletFile() method in SetExecutionUriAction.
It is still happening with build 200909211401
Please attach nps file . Your reasons could be different from described here. Actually it should be different because this issue is REALY fixed. Source code is changed so there cannot be the same profile backtrace.
Some of snapshots are not valid for now. So it is not so easy to identify the main reason of sleeping. But it seems I have found what action leads to this slowness. It appears when run is performed on Servlet file. As result method getServletMappings of SetExecutionUriAction is called. It asks web model which is not yet initialized . First access to web model (similar to problem with SetExecutionUriAction) is very long operation. As result this issue appears. In the opposite of original SetExecutionUriAction problem we cannot postpone access to web model in this case. So unfortunately this issue cannot be fixed silently from performance point of view. It appears as result of model scanning wait ( RUN action is always enable. We cannot disable it for period of initial scanning ). Only one way I see here : show dialog if scanning is not yet finished ( similar to initial Java scanning on refactoring action ). User will be able to cancel RUN action . It will unlock AWT thread. Either he can wait when scanning will be finished and proceed with RUN action.
changeset: 147917:606c241c8763 user: Denis Anisimov <ads@netbeans.org> date: Tue Oct 06 15:19:40 2009 +0400 summary: Fix for IZ#170419 - Invoking Run took 29110 ms. changeset: 147918:52cbed68eeac user: Denis Anisimov <ads@netbeans.org> date: Tue Oct 06 17:06:22 2009 +0400 summary: Fix for IZ#170419 is also applied for Debug action.
Integrated into 'main-golden', will be available in build *200910070250* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/606c241c8763 User: Denis Anisimov <ads@netbeans.org> Log: Fix for IZ#170419 - Invoking Run took 29110 ms.