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 252462 - org.netbeans.api.project.ProjectManager$2.run: LowPerformance took 22089 ms.
Summary: org.netbeans.api.project.ProjectManager$2.run: LowPerformance took 22089 ms.
Status: RESOLVED DUPLICATE of bug 253645
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Code (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Ondrej Vrabec
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2015-05-18 13:57 UTC by Exceptions Reporter
Modified: 2015-09-15 07:16 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 217376

Attachments
nps snapshot (35.39 KB, application/nps)
2015-05-18 13:57 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 2015-05-18 13:57:33 UTC 
This issue was reported manually by tstupka.
It already has 2 duplicates 


Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.75-b04, Java(TM) SE Runtime Environment, 1.7.0_75-b13
OS: Windows 7

User Comments:
GUEST: checking on windows updates and

alexx7676: Opening of a project



Maximum slowness yet reported was 47076 ms, average is 34582
Comment 1 Exceptions Reporter 2015-05-18 13:57:35 UTC 
Created attachment 153724 [details]
nps snapshot
Comment 2 Tomas Stupka 2015-05-18 14:20:17 UTC 
SharabilityQuery -> FileOwnerQuery -> ProjectManager.findProject
ProjectManager.findProjects eventually has to load a project and this might block AWT. 

please evaluate if sharability has to be called in sync with AWT
Comment 3 Ondrej Vrabec 2015-09-15 07:16:13 UTC 
I already disconnected building VCSContext in AWT when projects are being loaded. This is probably the same issue. If not and happens again, it will be reopened.

*** This bug has been marked as a duplicate of bug 253645 ***