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.xml.multiview.XmlMultiViewElement.getToolbarRepresentation: LowPerformance took 27998 ms. | ||
---|---|---|---|
Product: | platform | Reporter: | Exceptions Reporter <exceptions_reporter> |
Component: | Text | Assignee: | Miloslav Metelka <mmetelka> |
Status: | NEW --- | ||
Severity: | normal | Keywords: | PERFORMANCE |
Priority: | P3 | ||
Version: | 8.0 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 217010 |
Attachments: | nps snapshot |
Description
Exceptions Reporter
2015-04-28 23:20:58 UTC
Created attachment 153446 [details]
nps snapshot
The profiler snapshot shows that the Multiview impl. tries to get an editorPanel using CloneableEditor.getEditorPane(), which a/ MUST be called in AWT thread and b/ is BLOCKING until the editor initializes offscreen (CloneableEditorInitializer.waitForFinishedInitialization) I don't need the JEditorPane instance immediately, but the API does not provide a method (or I didn't find it) to find out that the editor pane is being initialized + potentially get notified when the init completes. Since getEditorPane() must be called in AWT, the caller risks UI freeze. (In reply to Svata Dedic from comment #2) > The profiler snapshot shows that the Multiview impl. tries to get an > editorPanel using CloneableEditor.getEditorPane(), which > a/ MUST be called in AWT thread and > b/ is BLOCKING until the editor initializes offscreen > (CloneableEditorInitializer.waitForFinishedInitialization) > > I don't need the JEditorPane instance immediately, but the API does not > provide a method (or I didn't find it) to find out that the editor pane is > being initialized Have a look at NbDocument.findRecentEditorPane > + potentially get notified when the init completes. have a look at CsmUtilities.openAtElement |