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 206456 - CodeCompletion took 2709 ms.
Summary: CodeCompletion took 2709 ms.
Status: RESOLVED DUPLICATE of bug 210539
Alias: None
Product: cnd
Classification: Unclassified
Component: Code Completion (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: issues@cnd
URL:
Keywords: PERFORMANCE
: 206455 206457 206458 206459 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-12-16 06:53 UTC by anba
Modified: 2012-04-12 11:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 183835

Attachments
nps snapshot (659.29 KB, application/nps)
2011-12-16 06:54 UTC, anba 		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 anba 2011-12-16 06:53:52 UTC 
This bug was originally marked as duplicate of bug 197270, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.1 RC2 (Build 201111302200)
VM: Java HotSpot(TM) Server VM, 20.4-b02, Java(TM) SE Runtime Environment, 1.6.0_29-b11
OS: Linux
Maximum slowness yet reported was 2709 ms, average is 2709
Comment 1 anba 2011-12-16 06:54:11 UTC 
Created attachment 114249 [details]
nps snapshot
Comment 2 Petr Cyhelsky 2012-02-08 13:22:32 UTC 
*** Bug 206455 has been marked as a duplicate of this bug. ***
Comment 3 Petr Cyhelsky 2012-02-08 13:22:44 UTC 
*** Bug 206457 has been marked as a duplicate of this bug. ***
Comment 4 Petr Cyhelsky 2012-02-08 13:22:59 UTC 
*** Bug 206458 has been marked as a duplicate of this bug. ***
Comment 5 Petr Cyhelsky 2012-02-08 13:23:12 UTC 
*** Bug 206459 has been marked as a duplicate of this bug. ***
Comment 6 Dusan Balek 2012-04-12 09:18:21 UTC 
As can be seen from the snapshots attached in the Exception Reports, Code Completion is waiting for slow CsmCompletionProvider. Reassigning.
Comment 7 Vladimir Voskresensky 2012-04-12 11:05:05 UTC 
It is a known bug, but thanks for the report anyway!

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