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.
Start up 6.7rc2. Scanning project continues forever.
Created attachment 83482 [details] messages.log
Created attachment 83483 [details] Screen cap showing scanning project after 10 mins. after start up
Could you please start the IDE with -J-Dorg.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.level=FINE and attach here the messages.log again. The switch turns on logging of indexing activity. Thanks
Created attachment 83954 [details] messages.log with the suggested switch. This time it took 3 mins.
Thanks for the log file. It shows: Complete indexing of 603 binary roots took: 21452 ms Complete indexing of 119 source roots took: 93485 ms which suggests that the indexing finished in approx. 2 minutes. The log file also shows that the classpath roots have already been scanned (probably in the previous IDE session) and so the scanning only did the up-to-date check. After the initial scan I don't see any further activity in the log file. Is the IDE really scanning? Is the log file corresponding to the situation that you reported? Thanks
Created attachment 84023 [details] Another messages.log
This time: Complete indexing of 636 binary roots took: 25217 ms Complete indexing of 157 source roots took: 159968 ms Altogether, from starting of IDE to end of scanning (the progress bar disappearing), was about 6 mins.
Created attachment 84033 [details] messages.log from new installation of 6.7rc3. Started IDE at 2:02; scanning stopped at 2:25. Inconsistent.
Restarted 6.7rc3 after encountering bug 167681 and scanning projects hasn't stopped after 25 minutes. Started at 2:43, the scanning is still going at 3:08. I am unable to attach debugger (JPDA) with the scan going, and I do not see a button to stop the scan. Raising priority to P2.
Created attachment 84038 [details] messages.log for 6.7rc3
Scanning finally finishes at 3:13. This is extremely frustrating.
Created attachment 84039 [details] messages.log for 6.7rc3 after scan finally completes after 30 minutes.
Complete indexing of 635 binary roots took: 12221 ms Complete indexing of 72 source roots took: 1650360 ms Totaling to approx 28 minutes. I'm not sure why source roots indexing took so long.
Created attachment 84208 [details] messages.log for 6.7 release (not RC); started at 11:40 and scanning stopped at 12:04 (24 mins)
FYI, my environment: AMD Athlon 64 X2 Dual Core Processor 5200+, 2.59 GHz, 3.00 GB RAM, 139 GB HD with 98.4 GB free. Windows XP Pro with SP3.
Created attachment 84957 [details] Here it is again: 17 minutes to scan. WTH??
I confirm this bug. Reproduced (several times) in NetBeans 6.8 dev. It took 19 minutes to finish projects scanning after IDE startup. This is a terrible bug that happens several times a week and NB 6.8 must not have this bug in order to be released - hence I raise the priority to P1. The profiler reports that some 92% of time was consumed by method Throwable.getStackTrace(). I will attach a typical thread-dump that I get during scanning. -- NetBeans IDE Dev (Build 090722) (#aad0b72b6a5c) JDK 6u14, 64-bit, server VM Linux (Debian Lenny), 64-bit, Intel CPU (Core 2 Extreme - quad-core @ 3.0 GHz)
Created attachment 85057 [details] thread-dump (generated by jstack)
This long scan happened after I updated by IDE to a new development build (built locally). But after next update, the scan took just a few seconds. So this bug seems to be random.
Marian, please create new report (give it P1 if you wish). This can be (and most probably is) something different than whan Frank is reporting. Marian has apisupport project while Frank has web and plain java project if I am not mistaken. Marian, please attach more thread dumps - we would like to check whether it always ends in apisupport code. Also please run with the following system property set: -J-Dorg.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.level=FINE Frank, could you possibly try working with your projects in a 6.8 development builds and check whether the problem is still there. Please note that the dev builds are not suitable for real work, just for testing new version of NetBeans. Please grab a copy of 6.8 build here (if you want to help of course): http://bits.netbeans.org/download/trunk/nightly/latest/
Mariane, what have you reported is being filed right now by Vita as #169040.
Marian's problem was reported as issue #169040 and AFAIK it's already fixed. Frank, please use 6.8 dev build or the upcoming beta, if it's still slow for you please run the IDE with -J-Dorg.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.level=FINE and attach here new log files. Thanks