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 214616 - CodeCompletion took 2054 ms.
Summary: CodeCompletion took 2054 ms.
Status: RESOLVED WONTFIX
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-06-22 10:14 UTC by pprikryl
Modified: 2012-08-31 08:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 189916

Attachments
nps snapshot (43.09 KB, application/nps)
2012-06-22 10:14 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 pprikryl 2012-06-22 10:14:42 UTC 
This bug was originally marked as duplicate of bug 170858, 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 201206110001)
VM: Java HotSpot(TM) 64-Bit Server VM, 20.0-b11, Java(TM) SE Runtime Environment, 1.6.0_25-b06
OS: Windows 7
Maximum slowness yet reported was 2054 ms, average is 2054
Comment 1 pprikryl 2012-06-22 10:14:49 UTC 
Created attachment 121209 [details]
nps snapshot
Comment 2 Milos Kleint 2012-08-31 08:51:48 UTC 
MavenForBinaryQuery.Result accesses the MavenProject instance that needs to be loaded using the maven embedder. That's a clear case when the MavenProject instance associated project was de-references due to low memory (it's held via SoftReference). The next time we reach for MavenProject, the use absorbs the penalty.

The MavenProject instance is usually created right at the beginning when the project gets loaded, and only disappears when memory is really low. Not much we can do here.