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 174069 - [68cat] Invoking Options took 4860 ms.
Summary: [68cat] Invoking Options took 4860 ms.
Status: RESOLVED DUPLICATE of bug 167199
Alias: None
Product: platform
Classification: Unclassified
Component: Options&Settings (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jiri Skrivanek
URL: http://statistics.netbeans.org/except...
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2009-10-08 13:14 UTC by stefan79
Modified: 2009-10-12 12:43 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 159795

Attachments
nps snapshot (22.26 KB, bin/nps)
2009-10-08 13:14 UTC, stefan79 		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 stefan79 2009-10-08 13:14:31 UTC 
This issue was originally marked as duplicate of issue 167199, that is already resolved. This issue is still valid, so this seems to be another issue, but it might be related.

Build: NetBeans IDE Dev (Build 200910071536)
VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Windows XP, 5.1, x86

User Comments:
stefan79: Opened Options-Window.


Maximum slowness yet reported was 4860 ms, average is 4860
Comment 1 stefan79 2009-10-08 13:14:36 UTC 
Created attachment 89091 [details]
nps snapshot
Comment 2 Jiri Skrivanek 2009-10-08 14:11:11 UTC 
In issue 167199 I added wait cursor when Options dialog is about to open. According to T.Hurka's presentation I thought
it is enough for actions from 3 to 10s. Am I wrong?
Comment 3 Jindrich Sedek 2009-10-12 12:16:51 UTC 
You are right while there is a wait cursor, 10s is acceptable.

The problem in latest snapshot is that you spend 3s in AWT while calling "CategoryModel.getCurrentCategoryID" and you 
show wait cursor in OpenDisplayer.open() method that is called after that and it is already too late. 

You should take CategoryModel.getCurrentCategoryID out of AWT thread.
Comment 4 Jiri Skrivanek 2009-10-12 12:43:11 UTC 
Wait cursor is already displayed when "CategoryModel.getCurrentCategoryID" is called. It doesn't make sense to move it
out of AWT thread because user is waiting for appearing of the Options window anyway.

*** This issue has been marked as a duplicate of 167199 ***