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 192573 - [70cat] LowPerformance took 10320 ms.
Summary: [70cat] LowPerformance took 10320 ms.
Status: CLOSED WORKSFORME
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 7.0
Hardware: All All
: P1 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2010-11-27 17:28 UTC by diealp
Modified: 2011-05-26 12:17 UTC (History)
53 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 174380

Attachments
nps snapshot (5.03 KB, application/nps)
2010-11-27 17:28 UTC, diealp 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description diealp 2010-11-27 17:28:30 UTC 
Build: NetBeans IDE 7.0 Beta (Build 201011152355)
VM: Java HotSpot(TM) 64-Bit Server VM, 17.1-b03-307, Java(TM) SE Runtime Environment, 1.6.0_22-b04-307-10M3261
OS: Mac OS X

User Comments:
marcotts: debugging a j2me project

GUEST: executando um projeto inicial usando a plataforma netbeans, havia criado um botao e uma textarea nele

diealp: Switching to NetBeans after some minutes working in another application (Firefox)... after the switch NetBeans was slow and no responsive doing HTML checking for an half minute.



Maximum slowness yet reported was 21481 ms, average is 9907
Comment 1 diealp 2010-11-27 17:28:33 UTC 
Created attachment 103403 [details]
nps snapshot
Comment 2 Marian Mirilovic 2011-05-24 15:00:05 UTC 
257 reports and still coming ... reassign to performance team for evaluation
Comment 3 Petr Cyhelsky 2011-05-26 11:31:08 UTC 
It seems that this is another dump issue where a lot of slowness reports which have nothing in common get clumped together because they don't have any suspicious method or last action. The bad logic in  Exception reporter was recently fixed so this shouldn't be a problem anymore. See Issue #17927. Also this issue got only 1 new exception report in last two months so it seems this is no longer big problem. Closing as fixed.