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 228705 - NetBeans "Background scanning of projects" makes code completion not work
Summary: NetBeans "Background scanning of projects" makes code completion not work
Status: RESOLVED INCOMPLETE
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 7.4
Hardware: PC Linux
: P1 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-18 12:45 UTC by janario
Modified: 2013-04-24 12:19 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE log (64.35 KB, text/plain)
2013-04-18 12:45 UTC, janario 		Details
<no description> (37.76 KB, application/octet-stream)
2013-04-18 12:47 UTC, janario 		Details
<no description> (40.61 KB, application/octet-stream)
2013-04-18 12:47 UTC, janario 		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 janario 2013-04-18 12:45:07 UTC 
Sometimes, at least twice or three times a day, NetBeans starts scanning my open project and still on that for more than 5 minutes.
The problem is that when it is scanning I can't use code completion anymore. It takes a lot of time trying to find a completion and the result doesn't work or only work for already imported classes.

Product Version = NetBeans IDE Dev (Build 20130418-e7740401069c)
Operating System = Linux version 3.5.0-27-generic running on amd64
Java; VM; Vendor = 1.7.0_17
Runtime = Java HotSpot(TM) 64-Bit Server VM 23.7-b01
Comment 1 janario 2013-04-18 12:45:15 UTC 
Created attachment 133565 [details]
IDE log
Comment 2 janario 2013-04-18 12:47:31 UTC 
Two thread dumps from the same scanning
Comment 3 janario 2013-04-18 12:47:38 UTC 
Created attachment 133566 [details]
<no description>
Comment 4 janario 2013-04-18 12:47:44 UTC 
Created attachment 133567 [details]
<no description>
Comment 5 misterm 2013-04-18 12:49:55 UTC 
I can confirm this happens and it seems to be in a loop, because I can see in the progress task it is scanning all source roots and then starting it over again...
Comment 6 janario 2013-04-18 12:54:38 UTC 
As you can see in thread dump both are from the same scanning
2013-04-18 09:38:21 First thread dump
2013-04-18 09:45:16 Second thread dump
Comment 7 Petr Cyhelsky 2013-04-24 11:29:25 UTC 
Can you please instead of thread dumps attach .npss snapshot and messages log from the same run (as the snapshot).

btw. why are u using XX:MaxPermSize=1024m ? Were you getting OoME:Perm space exceptions? Otherwise it is better to keep default (much lower) setting.
Comment 8 janario 2013-04-24 12:19:33 UTC 
I don't remember why I put this PermSize. 
I think I have some exception. I'll put back the default and see what happens