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 185106 - LowPerformance took 3110 ms.
Summary: LowPerformance took 3110 ms.
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: Embedded Mozilla (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2010-04-27 14:58 UTC by azizur
Modified: 2012-06-25 07:05 UTC (History)
8 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 161814


Attachments
nps snapshot (9.60 KB, application/nps)
2010-04-27 14:58 UTC, azizur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description azizur 2010-04-27 14:58:42 UTC
Build: NetBeans IDE Dev (Build 201004270201)
VM: Java HotSpot(TM) Client VM, 16.3-b01, Java(TM) SE Runtime Environment, 1.6.0_20-b02
OS: Windows XP

User Comments:
GUEST: opening a css file.

GUEST: Moving files around

GUEST: It happens all the time, when I run NetBeans and try to open any document

facilityderek: Opening a large css file that contains "errors" ( nonstandard tricks for MSIE brower compatibility )

GUEST: I dragged a css file into netbeans and it got delayed. Before dragging I was working with php files. There were more than 20 php files open in netbeans.



Maximum slowness yet reported was 11703 ms, average is 5489
Comment 1 azizur 2010-04-27 14:58:48 UTC
Created attachment 98144 [details]
nps snapshot
Comment 2 Marek Fukala 2010-04-27 15:48:48 UTC
There are two kinds of problem in the snapshots:

1) there is a heavy classloading triggered from the CssPreviewTopComponent initialization

2) EmbeddedBrowserFactory.getDefault() called in the class constructor takes a lot of time 
 
I've deferred the SAXParser initialization done in the constructor (which could possibly trigger the heavy classloading) to later times: web-main#7d1e541e371c

Now what can possibly cause #1 is loading of the EmbeddedBrowser classes, the problem #2 is caused by the embedded browser, reassigning there
Comment 3 Quality Engineering 2010-04-28 05:04:19 UTC
Integrated into 'main-golden', will be available in build *201004280200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/
User: 
Log: