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.
Try this: 1) open a large project group. Scanning projects starts, ok. 2) you immediately change your mind, maybe because you opened the wrong group, and go to File -> Project Group -> none, to close it, while it is still scanning. 3) scanning projects will continue to run (not sure if indefinitely) after the project group closed, even though at this point the project tab has no projects to be scanned.
Reassigning to parsing and indexing infrastructure.
I assume you are using Netbeans 6.7 (beta or a recent dev build). Could you please run your IDE with -J-Dorg.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.level=FINE flag (eg. <nbinst>/etc/netbeans.conf), reproduce the problem and attach <ide-userdir>/var/log/messages.log file here. Thanks
Not really, i was using 6.5. Must have missed to set the version when i opened this issue. Setting it now to 6.5.
Ok, thanks.
*** Issue 167965 has been marked as a duplicate of this issue. ***
*** Issue 169444 has been marked as a duplicate of this issue. ***
I also quite frequently see scanning continue for quite a while (and on numerous source roots) after all projects have been closed.
*** Bug 181005 has been marked as a duplicate of this bug. ***
*** Bug 182160 has been marked as a duplicate of this bug. ***
Changing to P2 because it is really unpleasant. My scenario: - at work, I have a group with NB modules - at home, I usually use a group with a PHP project If I forget to switch to a "PHP" group before I leave work, then at home, I have to wait really looong time because NB modules are being scanned and there's no way to avoid/stop it (changing a group does not help at all). Thanks a lot.
A few of the duplicates state that just closing the project triggers scanning. This bug says the scanning was happening when they closed the project and closing the project didn't cancel the scanning, which may be as designed but is still probably undesirable (after all, when you reopen the project it's going to scan it anyway, right, so who cares if you stopped scanning half way through when the project was closed? Anyway, triggering a scan on a project when the project is closed is definitely a bug and needs to be addressed.
*** Bug 174821 has been marked as a duplicate of this bug. ***
*** Bug 179965 has been marked as a duplicate of this bug. ***
I'm also seeing this issue with 6.9.1...
*** Bug 196390 has been marked as a duplicate of this bug. ***
Please evaluate : if you do not plan to fix it for NB 7.0 ask for waiver ASAP.
In fact the scan is stopped after finishing the unit of work (root) when the source group is switched. The currently running RootsWork is canceled by a new one and when the root is done it finishes. Canceling indexer in the source root is not desired because of cost of restart. The problem is with successive index update (Refresh Index) scheduled by the indexers. If the indexers of the current running RootsWork schedule some RefreshIndex(es) these are executed. The cancel should kill all such works.
Fixed jet-main f2c6f9ea6c8a Fixed in trunk , if it should be integrated into 7.0, qa should do testing. And the patch needs peer review as its context is quite complicated.
Ok, thanks for fixing. In my opinion it's too risky for current release, so I would like to postpone it till NB 7.0.1 (next patch release). I agree with WAIVER for NB 7.0
Integrated into 'main-golden', will be available in build *201103290400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/f2c6f9ea6c8a User: Tomas Zezula <tzezula@netbeans.org> Log: #165093:Scanning projects should end after closing project group
*** Bug 170521 has been marked as a duplicate of this bug. ***