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.
Summary: | [68cat] Invoking Options took 4860 ms. | ||
---|---|---|---|
Product: | platform | Reporter: | stefan79 <stefan79> |
Component: | Options&Settings | Assignee: | Jiri Skrivanek <jskrivanek> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | hmichel, jsedek, jskrivanek, stefan79 |
Priority: | P3 | Keywords: | PERFORMANCE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://statistics.netbeans.org/exceptions/detail.do?id=159795 | ||
Issue Type: | DEFECT | Exception Reporter: | 159795 |
Attachments: | nps snapshot |
Description
stefan79
2009-10-08 13:14:31 UTC
Created attachment 89091 [details]
nps snapshot
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? 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. 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 *** |