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: | LowPerformance took 14923 ms. | ||
---|---|---|---|
Product: | cnd | Reporter: | Exceptions Reporter <exceptions_reporter> |
Component: | Navigation | Assignee: | Alexander Simon <alexvsimon> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexvsimon, dstrupl |
Priority: | P3 | Keywords: | PERFORMANCE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 166410 |
Attachments: | nps snapshot |
Description
Exceptions Reporter
2010-03-15 09:21:38 UTC
Created attachment 95161 [details]
nps snapshot
Hello, please check similar fix here: http://hg.netbeans.org/main/rev/8d9f9559cb00 The point is not to call getOpenedPanes (getEditorPane) in order not to cause the editor initialization when it is not ready. There should be alternative calls that will not cause the initialization and return null instead on NbDocument (findRecentEditorPane). How did it get into QNavigator category? Should we go ahead and remove this category? our navigator is in cnd.qnavigator module I put it to that category based on package name. Feel free to move anywhere you like provided that someone from your team will have a look at it ;-) fixed, change set: http://hg.netbeans.org/cnd-main/rev/e682d213bbb6 *** Bug 182718 has been marked as a duplicate of this bug. *** |