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.

Bug 170858

Summary:	32s in refresh of MainProjectAction
Product:	projects	Reporter:	jmichelberger <jmichelberger>
Component:	Generic Infrastructure	Assignee:	Jesse Glick <jglick>
Status:	RESOLVED WORKSFORME
Severity:	blocker	CC:	lucianomarcio, sebglon
Priority:	P4	Keywords:	PERFORMANCE
Version:	6.x
Hardware:	All
OS:	All
URL:	http://statistics.netbeans.org/exceptions/detail.do?id=156766
Issue Type:	DEFECT	Exception Reporter:	156766
Attachments:	nps snapshot

Description jmichelberger 2009-08-25 09:42:26 UTC

Build: NetBeans IDE Dev (Build nbms-and-javadoc-3779-on-090820)
VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Windows XP, 5.1, x86
Maximum slowness yet reported was 32642 ms, average is 32642

Comment 1 jmichelberger 2009-08-25 09:42:40 UTC

Created attachment 86607 [details]
nps snapshot

Comment 2 Milan Kubec 2009-09-08 14:25:09 UTC

IMO most of the time spent in IO operations. Please re-evaluate. Thanks.

Comment 3 Jaroslav Tulach 2009-09-09 07:08:00 UTC

Clearly, the calls are initiated from MainProjectAction as a reaction to switching of tabs. While tabs have to be 
switched in AWT thread, there is not much reasons why MainProjectAction would have to refresh its state in the same 
thread. It may do this outside of AWT. Otherwise we risk that calls to ActionProvider's will take really long time 
(like in this case the calls to SuiteActions do).

Comment 4 Milan Kubec 2009-10-02 12:54:23 UTC

Lowering priority of this issue, since it's only one single report and majority of the time is spent in simple native
filesystem call.

Comment 5 Antonin Nebuzelsky 2010-03-29 14:11:08 UTC

Change of default owner.

Comment 6 Jesse Glick 2012-03-26 23:12:13 UTC

*** Bug 205523 has been marked as a duplicate of this bug. ***

Comment 7 Jesse Glick 2012-03-26 23:22:56 UTC

*** Bug 198246 has been marked as a duplicate of this bug. ***

Comment 8 Petr Cyhelsky 2012-06-01 08:15:45 UTC

Last report came from 7.1 RC2 - seems to be fixed, please reopen if it occurs again