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've got into situation when Delete Project dialog was opened at 50% and it wasn't never closed. It was probably caused by the fact that classpath scanning was started at the same time. I hope thread dump and screen shot will be helpful because I can't reproduce it anymore. I didn't do anything special. Just create several java projects and then delete one of them. Build 20051206-0733, WindowsXP, JDK1.5.0_05.
Created attachment 27583 [details] Thread dump
Created attachment 27584 [details] Screen shot
The dialog was not closed after the classpath scanning finished? Anyway, there is probably nothing that can be done in projects, the delete process is not finished and waits for a java's mutex, so the dialog cannot be closed.
> The dialog was not closed after the classpath scanning finished? I don't understand this question. From screen shot it seems classpath scanning started when the dialog was open.
Well, the process of project delete is blocked by the classpath scanning, but once the scanning finishes the project delete should finish and the dialog should be closed. Does this happen? (BTW: I neither know why the scan started nor why the transaction is started inside a file deleted listener, but it is not a problem of project delete.)
No, it stayed as shown in screen shot. If this is not your issue, please re-assign.
Aha, the situation is: -the project delete starts. -the classpath scanning starts. -the classpath scanning never finishes. I do not think this is problem in project delete: it simply deletes a file, but this is blocked by a listener. Passing to java/javacore for further evaluation.
Really strange issue. In fact classpath scanning does not start. All threads are waiting for ExclusiveMutex, but none holds it. jskrivanek, did you use regular builds? Did you use any additional modules?
Issue #65815 shows the similar behaviour. Moreover, recently Petr Nejedly saw this problem too. We have to think about some logging (to be able to see in log who last entered the transaction). #65815 and Petr's was observable in build with Collab installed. (There is nothing related with our transaction in collab, but it can be better reproducible with this support.)
> jskrivanek, did you use regular builds? Did you use any additional modules? It was continuous build 20051206-0733 (on WindowsXP, JDK1.5.0_05) started with fresh userdir and only several java projects were created.
Javacore module was replaced by Retouche infrastructure. This bug is not valid in trunk any more.
Verified.
Reorganization of java component