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.
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
Created attachment 91962 [details] nps snapshot
This might be a duplicate of issue #190604.
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
(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.
the 7.3 cases so far are among others caused by slow native IO apparently during classloading.
http://hg.netbeans.org/core-main/rev/f2927475bfa1
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.