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.
I created a very simple project, edited the main class. Then I opened project properties and modified the run arguments to be -w c:\foo The OK button stayed depressed with the AWT thread hung for about 30 seconds. I changed the settings again, and the same thing happened - seems to be 100% reproducible. Thread dump attached.
Created attachment 40292 [details] thread dump
P2 given that it's a very common operation and the hang makes a very bad impression.
It does xslt transformation, event firing. Maybe there should be a progress
> Maybe there should be a progress Not only that. The code needs to be rescheduled, it blocks AWT!
Caused by excludes. The ClassPath was changed to call ClassPathImplementation.getResources() in the SPIListener (called synchronously from the AWT). The getResources() may be expensive for GlobalSourcePath - it calls SFBQ which is slow. The only thing which may help is to fire changes from GlobalSourcePath asynchronously - probably doesn't matter. Checking in org/netbeans/modules/java/source/classpath/GlobalSourcePath.java; /cvs/java/source/src/org/netbeans/modules/java/source/classpath/GlobalSourcePath.java,v <-- GlobalSourcePath.java new revision: 1.10; previous revision: 1.9 done