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 218662

Summary: Background scanning starts on code completion try (Ctrl+Space), shows 'Please wait', and lasts forever.
Product: editor Reporter: stasam
Component: Completion & TemplatesAssignee: stasam
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: P2    
Version: 7.2   
Hardware: PC   
OS: Windows 7 x64   
Issue Type: DEFECT Exception Reporter:
Attachments: NB var/log/messages.log
NB 7.2 profiler snapshot

Description stasam 2012-09-20 08:02:06 UTC
Created attachment 124621 [details]
NB var/log/messages.log

Product Version: NetBeans IDE 7.2 (Build 201207171143)
Java: 1.6.0_31; Java HotSpot(TM) 64-Bit Server VM 20.6-b01
System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)

When I try code completion (Ctrl+Space) on references which point to JPA entity objects, NB shows "Please wait..." message, and netbeans64.exe process takes constantly about 25% of CPU time. It never finishes.
I can cancel code completion "Please wait...", but it is unusable anywhere in the code until NB is restarted. 25% CPU time consumption also lasts forever, until NB is restarted.

Problem is manifested always. I have to restart NB every time when I try code completion on JPA entities or JPQL queries. NB doesn't freeze, it just takes CPU time, and code completion starts to be unusable from that moment.
Comment 1 Dusan Balek 2012-09-20 14:10:57 UTC
Could you please create a profiler snapshot (using Profile the IDE action - Alt+Shift+Y) and attach it to the issue? Thanks.
Comment 2 stasam 2012-09-21 07:23:04 UTC
Created attachment 124679 [details]
NB 7.2 profiler snapshot

Snapshot added.
Comment 3 stasam 2012-09-21 08:12:10 UTC
I tried to reproduce the same problem in NB dev 201209200001 release, unsuccessfully. In that release, code completion works. Can you confirm that the problem is fixed in the mean time?
Comment 4 Dusan Balek 2012-09-21 08:37:51 UTC
Should be already fixed. See issue #216053 for more details.

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