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 169666 - Scanning never stops when switching project groups
Summary: Scanning never stops when switching project groups
Status: RESOLVED DUPLICATE of bug 170521
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vitezslav Stejskal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-31 22:52 UTC by tkellerer
Modified: 2009-09-04 08:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 tkellerer 2009-07-31 22:52:11 UTC 
When I switch from one project to group to another (especially if the target group contains a large project) scanning
never stops (I killed NB after 30 minutes)

Scanning right after a re-start finishes in about 20-40 seconds (depending on the project)

NetBeans 6.7.1 (without the recent updates)
Windows XP, JDK 1.6.0_14
Comment 1 Milos Kleint 2009-08-03 12:22:04 UTC 
reassigning to java. How does the scanning/parsing infrastructure decide when to scan and what? what are the triggers?
AFAIK the changing of groups just means closing a set of project and opening a different set of projects..
Comment 2 Rastislav Komara 2009-08-04 10:47:17 UTC 
@vstejskal: Please can you answer the questions by mkleint. Thank you.
Comment 3 tkellerer 2009-08-07 10:24:11 UTC 
It seems that the project size is not necessarily the reason. 
It seems that projects that have more than one source directory are affected.
Comment 4 David Strupl 2009-09-03 14:51:47 UTC 
Some of the answers to Milos' questions can be found here:

http://wiki.netbeans.org/EditorIndexing68

Without reproducible test case we are out of luck of fixing this. The suspision about more source roots is a good one
but we need a bit more to be able to analyze. Can someone who is experiencing this please run with

-J-Dorg.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.level=FINE

and attach the results to this bug? I am marking this report as incomplete for now ..
Comment 5 Vitezslav Stejskal 2009-09-04 08:26:34 UTC 
David, we seem to have a reproducible usecase, see issue #170521.

*** This issue has been marked as a duplicate of 170521 ***