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 198087

Summary:	LowPerformance took 75577 ms.
Product:	javaee	Reporter:	Exceptions Reporter <exceptions_reporter>
Component:	EJB Project	Assignee:	David Konecny <dkonecny>
Status:	RESOLVED WONTFIX
Severity:	normal	CC:	jglick, jocke, jtulach, marfous
Priority:	P3	Keywords:	PERFORMANCE
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	162263
Attachments:	nps snapshot

Description Exceptions Reporter 2011-04-26 13:12:46 UTC

Build: NetBeans IDE 6.9.1 (Build 201011082200)
VM: Java HotSpot(TM) Client VM, 10.0-b22, Java(TM) SE Runtime Environment, 1.6.0_06-b02
OS: Windows XP
Maximum slowness yet reported was 75577 ms, average is 39760

Comment 1 Exceptions Reporter 2011-04-26 13:12:53 UTC

Created attachment 107945 [details]
nps snapshot

Comment 2 Martin Fousek 2011-04-28 09:02:48 UTC

From the last snapshots it seems that ActionStateUpdater.actionPerformed() invoke update of all node actions in EDT which is blocked by project save by its closing - saveProject() acquires writeAccess on the same mutex as is needed for reading by update of all actions. I will talk to t_h who contributed on this place and eventually reassign this issue.

Comment 3 Martin Fousek 2011-04-28 11:38:48 UTC

I'm reassigning the issue since it looks like Explorer API problem.

Comment 4 Jaroslav Tulach 2011-05-03 08:21:33 UTC

May I get an explanation why the issue is supposed to be problem in explorer? I see 65s wasted in EJB.

Comment 5 Martin Fousek 2011-05-03 09:52:14 UTC

Right, the delay seems to be rising in EJB, but actually it's coming between ExplorerActionsImpl.updateActions which leads to BaseActionProvider.isActionEnabled and ProjectManager.saveProject.

Especially now it looks to me as badly reassigned as well, sorry for that. :/ 
It is related to Projects. I took a look quickly into WEB, EJB projects and in both of them it could happen. Generally it can happen for any BaseActionProvider subtype.

Comment 6 Jaroslav Tulach 2011-05-04 07:25:37 UTC

Jesse, as designer of ActionProvider.isActionEnabled and other project code, shall advice you how to make the call non-blocking.

Comment 7 Jesse Glick 2011-05-05 21:33:25 UTC

According to the snapshot, 64 seconds is being spent in a single call to ClassLoader.getResourceAsStream - which would seem to indicate that the user's JVM is out of file handles, at max heap, swapped out, or otherwise pretty much busted. If so, there is nothing to be done in IDE code.

Comment 8 Martin Fousek 2011-05-10 12:09:52 UTC

Ok, totally agree. Closing as WONTFIX for now but jocke feel free to reopen if you would be able to reproduce it without exhausted resources. Thanks.