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.
070524. I had opened a file from serverplugins/sun/appsrv81 and that project. Source scanning began. When scanning websvc/jaxwsmodel/src, it just went to 100% CPU (on one of two CPUs) and stayed there, with no apparent progress. I took a thread dump. Then I clicked the close button on the IDE main window; at this point the GUI froze. Second thread dump demonstrates why - JBrowseModule.closing is waiting for scanning to complete. (It should not; core/execution will anyway offer to wait for or kill outstanding processes, in this case from the Progress API.)
Created attachment 42975 [details] Two thread dumps
After killing and reopening the IDE, hangs again on websvc/jaxwsmodel/src. Don't know what is wrong with this project - it's not particularly big or anything.
After killing the IDE again, clearing my userdir's cache, and reopening the IDE, still hangs on the same source root. This time I close the main window and I get a proper Exit dialog prompting me to wait for the scanning task. I choose to Exit immediately. Again IDE freezes.
Created attachment 42977 [details] More thread dumps
Adjusting summary. Perhaps there are two independent bugs here, but I'm not sure.
Two issues here, indeed: -never ending scanning of websvc/jaxwsmodel/src filed (and fixed) as issue #104831. Please use newer build. -IDE shutdown delayed (assuming the scan finishes) by scanning - not nice, but not P2, IMO.
In the past the RepositoryUpdater didn't react on events cuased by IDE close, unfortunately now these events are fired before ModuleInstall.isClosing() method is called. The RU does not know that the IDE is being closed.
I've talked about it with Radim. I need either some notification about IDE exit before the projects are closed or to delay closing of projects after all ModuleInstall.isClosing() are done. Maybe the projects shoudn't be closed when the IDE is exiting, no OpenProjectHook called, but it may be dangerous.
Fixed in RepositoryUpdater rev 1.64