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 177959 - [69cat] Invoking Run File took 3265 ms. mostly in classloading IO
Summary: [69cat] Invoking Run File took 3265 ms. mostly in classloading IO
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: Milos Kleint
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2009-12-01 19:42 UTC by manishgrg
Modified: 2013-06-27 02:19 UTC (History)
24 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 161704


Attachments
nps snapshot (256.00 KB, application/nps)
2009-12-01 19:42 UTC, manishgrg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description manishgrg 2009-12-01 19:42:49 UTC
Build: NetBeans IDE 6.8 Beta (Build 200910212001)
VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08
OS: Windows XP, 5.1, x86

User Comments:
manishgrg: Invoking three different threads in an light-weight basic application.


Maximum slowness yet reported was 5882 ms, average is 4148
Comment 1 manishgrg 2009-12-01 19:42:54 UTC
Created attachment 91962 [details]
nps snapshot
Comment 2 Martin Entlicher 2011-01-13 15:50:02 UTC
This might be a duplicate of issue #190604.
Comment 3 digitalrinaldo 2011-01-15 22:42:06 UTC
My issue 467495  was classified as part of this issue in 2009. I dont' think it has anything to do with it. I think the automated classifier is wrong. Unles all that is know that it took too long from Run to start of the action and nothing is known about the steps in between.  This is a recent change in NetBeans
Comment 4 Jesse Glick 2011-01-19 14:26:18 UTC
(In reply to comment #3)
> I think the automated classifier is wrong.

Quite possible; it does a pretty good job of aggregating exceptions, and generally a poor job of aggregating slowness snapshots. Usually these bug reports are a grab bag of unrelated (usually unreproducible) issues. For now I don't have time to evaluate them.
Comment 5 Milos Kleint 2012-11-26 13:43:53 UTC
the 7.3 cases so far are among others caused by slow native IO apparently during classloading.
Comment 6 Milos Kleint 2013-06-24 13:36:14 UTC
http://hg.netbeans.org/core-main/rev/f2927475bfa1
Comment 7 Quality Engineering 2013-06-27 02:19:02 UTC
Integrated into 'main-golden', will be available in build *201306262301* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/f2927475bfa1
User: Milos Kleint <mkleint@netbeans.org>
Log: #180542, #188382, #213607, #177959 actionPerformed() in lookupSensitiveAction subclasses posted to RP. In tests kept in AWT to avoid deleting them altogether. Might have problems primarily with lookup content changing between AWT and RP processing.