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 168498

Summary:	9,755 ms. - opened large HTML file
Product:	editor	Reporter:	Jesse Glick <jglick>
Component:	Painting & Printing	Assignee:	issues@editor <issues>
Status:	RESOLVED WONTFIX
Severity:	blocker	CC:	issues
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
URL:	http://statistics.netbeans.org/exceptions/detail.do?id=153658
Issue Type:	DEFECT	Exception Reporter:	153658
Attachments:	nps snapshot

Description Jesse Glick 2009-07-13 17:09:26 UTC

Build: NetBeans IDE Dev (Build 090708)
VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08
OS: Linux, 2.6.28-13-generic, i386

User Comments:
jglick: Opened a largish HTML file (hudson/www/changelog.html).


Maximal alredy reported slowness was 9755 ms, average is 9755

Comment 1 Jesse Glick 2009-07-13 17:09:38 UTC

Created attachment 84669 [details]
nps snapshot

Comment 2 Jesse Glick 2009-07-13 17:26:05 UTC

Seems to just be loading fonts; maybe unavoidable.

Comment 3 Vitezslav Stejskal 2009-09-03 15:32:08 UTC

Agreed. There was no Nb code running in AWT.

Comment 4 Jaroslav Tulach 2009-09-03 16:42:52 UTC

Common guys, you could call JComponent.getFontMetrics() (or equivalent) outside of AWT in NbSomeKit.call() method 
which would move these 9s to more acceptable place (I mean background thread).

Comment 5 Vitezslav Stejskal 2009-09-03 18:02:51 UTC

"Common guys, you could call JComponent.getFontMetrics() (or equivalent) outside of AWT in NbSomeKit.call() method" - I
believe we do so since http://hg.netbeans.org/main-golden/rev/ce68e18c844d.
 
"which would move these 9s to more acceptable place (I mean background thread)." - I can't tell that from this
particular snapshot, because it gives no evidence that any of the code installing editor kits was running. Anyway, it's
either fixed by #ce68e18c844d (and technically dupe of issue #170423) or WONTFIX, because I don't know what to optimize.
Moreover, if this were a serious problem we would have many duplicate profiler snapshots. So far we have got one since
13-Jul-2009.