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.
When starting Netbeans 7.2.1 the background scanning of projects gets stuck at 67% and does not end when the stop (x) is clicked. I had experienced the same problem in 7.3 Beta which rendered the IDE unusable so I uninstalled it and installed the latest stable release, the problem remains however.
Please can you attach the IDE self profile when the scanning hangs? Here is a description how to do it: http://wiki.netbeans.org/FitnessViaPartnership Without the snapshot it's impossible to find out what happened. Thanks
this bug has been posted by many others as far back as July 2012. http://forums.netbeans.org/topic50321.html Can you please tell me in what context this bug is "resolved"?
Resolved incomplete means that additional input is required from the reporter, see comment #1. Before kenai migration there was an keyword incomplete unfortunately it has changed. Now it's a resolved incomplete status which may be misleading as it's resolved. The reported should attach the required data and reopen the issue which is a bit more complicated as it was.
Thanks for your explanation, but in reality the matter is not resolved as you have agreed, so why Netbeans persists with this phrasing is unclear. I would attach the .npss snapshot if I were able to read the information it contains. Given that I can't I am reluctant to post it on a public forum.
Created attachment 129683 [details] .npss file attached from NetBeans .npss file
Cummulative stack depth 2566 ??? in com.thaiopensource.relaxng.impl.ChoicePattern... :)
The well known "thai towers" problem :-), it's duplicate of #206025. The attached snapshot file is not a hang on 67%, the indexing is finished, so it may be another problem than the original one. It's also questionable while the html tasks are calculated when most of users has Action Items (Task List) hidden. *** This bug has been marked as a duplicate of bug 206025 ***