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 205491

Summary:	4s - useless processing in CloseAllButThisAction.propertyChange
Product:	platform	Reporter:	vercinstex
Component:	Window System	Assignee:	Stanislav Aubrecht <saubrecht>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	_m4c0_
Priority:	P4	Keywords:	PERFORMANCE
Version:	7.1
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	162222
Attachments:	nps snapshot

Description vercinstex 2011-11-23 17:00:48 UTC

Build: NetBeans IDE Dev (Build 2011-11-23_09-04-33 )
VM: Java HotSpot(TM) Client VM, 20.4-b02, Java(TM) SE Runtime Environment, 1.6.0_29-b11
OS: Windows 7

User Comments:
_m4c0_: * clicking on "Output" window button with editor area maximized

GUEST: Scanning a PHP project with remote (LAN) sources



Maximum slowness yet reported was 249414 ms, average is 38766

Comment 1 vercinstex 2011-11-23 17:00:53 UTC

Created attachment 113484 [details]
nps snapshot

Comment 2 Jaroslav Tulach 2011-11-24 06:59:41 UTC

The longest report is 
http://statistics.netbeans.org/exceptions/exception.do?id=514765
and it seems to indicate the AWT thread is blocked on 
org.netbeans.modules.editor.indent.IndentImpl.indentLock() for 239383 ms.

Comment 3 Dusan Balek 2011-11-24 09:19:05 UTC

The longest report is a duplicate of #196753 (already fixed in NB 7.0.1). Since no other of the recent reports mentions the editor/indentation, returning back to filesytems.

Comment 4 Jaroslav Tulach 2011-11-24 10:14:17 UTC

OK, I made the report 514765 duplicate of http://statistics.netbeans.org/exceptions/detail.do?id=169474 then.

Then we have a report when one call to 
org.openide.actions.OpenAction.performAction()	100.0	3290 ms (100%)	2326 ms	1
results in 104 calls to 
org.openide.windows.TopComponent.open()	51.101692	1681 ms (51,1%)	1681 ms	104

Possibly a multiselection issue. ~700ms is waisted in 
org.netbeans.core.windows.actions.CloseAllButThisAction.propertyChange()	22.436134	738 ms (22,4%)	738 ms	71
and could be eliminated by using invokeLater once rather than updating the state immediatelly.

Comment 5 Stanislav Aubrecht 2012-09-19 15:31:16 UTC


*** This bug has been marked as a duplicate of bug 216454 ***