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 131395

Summary:	UML class diagram pauses for 1 or 2 seconds for no apparent reason.
Product:	uml	Reporter:	neilwightman <neilwightman>
Component:	General	Assignee:	issues@uml <issues>
Status:	VERIFIED WORKSFORME
Severity:	blocker	Keywords:	PERFORMANCE
Priority:	P3
Version:	6.x
Hardware:	All
OS:	Windows XP
Issue Type:	DEFECT	Exception Reporter:
Attachments:	Stack trace showing what the swing thread is calling.

Description neilwightman 2008-03-28 12:51:34 UTC

I've been working with the UML class diagram for a package, and it keeps pausing for 1 or 2 seconds when clicking in the UI.

Attached is a thread dump showing the Swing thread is busy calling
org.dom4j.tree.AbstractBranch.elementByID(AbstractBranch.java:241)
recursively.

In the Netbeans project we have 3271 src files and 1475 test files.  I performed a reverse engineer on the complete src
directory to generate the model information.

System info:
Product Version: NetBeans IDE 6.0 (Build 200711261600)
Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06
System: Windows XP version 5.1 running on x86; Cp1252; en_GB (nb)
Userdir: C:\Documents and Settings\nwightma\.netbeans\6.0

Do you need more information or is the stack trace enough?

Comment 1 neilwightman 2008-03-28 12:52:07 UTC

Created attachment 59281 [details]
Stack trace showing what the swing thread is calling.

Comment 2 neilwightman 2008-03-28 13:37:35 UTC

I checked in the project and the XML file Model.etd file is 32,407Kb.

Comment 3 neilwightman 2008-03-28 13:44:08 UTC

The more classes I add to the class diagram the worse it gets.

I have just 10 classes visible now and the UML diagram is unusable.  The pauses have gone up to over 30 seconds and this
pause seems to happen every single click in netbeans.

It appears that this scanning (dom4js elementById()) is n squared so as your project grows performance gets worse.

The need for correct UML diagrams is more important for larger projects, but this is when the tool fails.

Comment 4 Viktor Lapitski 2008-03-29 01:12:04 UTC

it was fixed in the same putback together with the fix 
for IZ 122550 on 2007/12/03. Please check out 6.1 release  
that contain the fix and some other perf improvements 
affecting diagram handling as well.

Comment 5 Peter Lam 2008-04-03 19:15:30 UTC

please try it again with the latest NB 6.1 build from the following link. If problem still exists, please reopen this
issue. Thanks.
http://bits.netbeans.org/netbeans/trunk/nightly/latest/

Comment 6 Peter Lam 2008-04-03 19:19:56 UTC

I meant to point to the following 6.1 RC1 build instead of the trunk build.

http://bits.netbeans.org/download/6.1/nightly/latest/