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 239892 - org.netbeans.modules.db.sql.loader.SQLCloneableEditor.getToolbarRepresentation: LowPerformance took 47141 ms.
Summary: org.netbeans.modules.db.sql.loader.SQLCloneableEditor.getToolbarRepresentatio...
Status: RESOLVED DUPLICATE of bug 207155
Alias: None
Product: projects
Classification: Unclassified
Component: Ant Project (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Milos Kleint
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2013-12-31 16:00 UTC by Exceptions Reporter
Modified: 2014-01-15 08:59 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 205877

Attachments
nps snapshot (171.85 KB, application/nps)
2013-12-31 16:00 UTC, Exceptions Reporter 		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 Exceptions Reporter 2013-12-31 16:00:44 UTC 
Build: NetBeans IDE 7.4 (Build 201310111528)
VM: Java HotSpot(TM) Client VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18
OS: Windows XP

User Comments:
pedropmp: I have no idea what happened

GUEST: <Please provide a description of the problem or the steps to reproduce>
scanning virus



Maximum slowness yet reported was 47141 ms, average is 38619
Comment 1 Exceptions Reporter 2013-12-31 16:00:49 UTC 
Created attachment 143540 [details]
nps snapshot
Comment 2 Libor Fischmeistr 2014-01-08 14:22:38 UTC 
I don't think the slowness is caused by DB, maybe by the project?

Reassigning for further evaluation.
Comment 3 Milos Kleint 2014-01-15 08:59:03 UTC 
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 ***