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 206874 - LowPerformance took 9930 ms. ClassPath.entries() loads a MavenProject
Summary: LowPerformance took 9930 ms. ClassPath.entries() loads a MavenProject
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Milos Kleint
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2012-01-03 14:28 UTC by FrantaM
Modified: 2013-06-20 09:30 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 184125

Attachments
nps snapshot (200.03 KB, application/nps)
2012-01-03 14:28 UTC, FrantaM 		Details
nps snapshot (129.45 KB, application/nps)
2012-06-13 12:49 UTC, pprikryl 		Details
nps snapshot (89.12 KB, application/nps)
2012-08-27 06:52 UTC, pprikryl 		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 FrantaM 2012-01-03 14:28:22 UTC 
This bug was originally marked as duplicate of bug 187919, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 201112270601)
VM: Java HotSpot(TM) 64-Bit Server VM, 21.0-b17, Java(TM) SE Runtime Environment, 1.7.0-b147
OS: Linux
Maximum slowness yet reported was 9930 ms, average is 9930
Comment 1 FrantaM 2012-01-03 14:28:29 UTC 
Created attachment 114582 [details]
nps snapshot
Comment 2 Dusan Balek 2012-01-05 15:33:58 UTC 
Code completion is waiting for extremely slow call to the ClassPath.entries()
which seems to be blocked by loading of a Maven project.
Comment 3 pprikryl 2012-06-13 12:49:53 UTC 
Created attachment 120781 [details]
nps snapshot
Comment 4 pprikryl 2012-08-27 06:52:58 UTC 
Created attachment 123594 [details]
nps snapshot
Comment 5 Milos Kleint 2013-06-20 09:30:16 UTC 
since 7.3 we hard reference MavenProject instance in the open project and soft reference it for closed projects, before that it was soft referenced all the time. When memory limit was reached such entries were released and then immediately reloaded. I believe that is the case in this issue as well. It should not be happening and indeed the recent reports were not related to maven, I've split them into separate reports.

closing as fixed