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: | org.netbeans.modules.db.sql.loader.SQLCloneableEditor.getToolbarRepresentation: LowPerformance took 47141 ms. | ||
---|---|---|---|
Product: | projects | Reporter: | Exceptions Reporter <exceptions_reporter> |
Component: | Ant Project | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | pedropmp |
Priority: | P3 | Keywords: | PERFORMANCE |
Version: | 7.4 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 205877 |
Attachments: | nps snapshot |
Description
Exceptions Reporter
2013-12-31 16:00:44 UTC
Created attachment 143540 [details]
nps snapshot
I don't think the slowness is caused by DB, maybe by the project? Reassigning for further evaluation. in both cases the AWT hangs on waiting for other thread to load the document/editor. one report hangs in single call to FileObject.getInputStream() via SqlFileEncodingQueryImpl, the other report is loading a project via SimpleFileOwnerQueryImplementation and the slowness is more spread out there's very little that can be done with the first report, a single IO event cannot take that long and the AWT is likely waiting for a good reason here. the second case is likely a duplicate of issue 207155, as long as we support loading projects outside of the opening loop (load projects that are not opened), especially projects loaded by FileOwnerQuery, we will get this kind of reports. Loading projects is not cheap, even though most of the work is already postponed. duplicate of issue 207155 but could also be wontfix. *** This bug has been marked as a duplicate of bug 207155 *** |