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.
NB build 200311130470 I tried to exit IDE and it frozen. I've seen it in automated tests run too (many times). It has a hard impact on the run of automated tests.
The build was 200311130740
Created attachment 12159 [details] Thread dump.
Jemmy/jelly related problem. The Jemmy uses a awt-qeue-2 thread. The thread is not stoped.
Hard impact means (in words of issue priority) P1. It blocks our test machines. Removing RANDOM kw according Petr's last comment.
I have reproduced it on Solaris.
IMO nothing to do with winsys.
Hint for jemmy guys. I moved the exit sequence in NbTopManager into AWT Thread (due to hiding and saving of winsys). It seems jemmy can't deal with such a circumstance.
Jemmy installs own EventQueue instance. I don't know if it can be a problem. Look at jemmy/src/org/netbeans/jemmy/QueueTool.JemmyQueue.
It seems it is caused by security check at the end of exit sequence in IDE. If I run the IDE with the -J-Dnetbeans.security.nocheck=true switch, it is not "locked". I will try to find a root of problems with core specialist.
Created attachment 12231 [details] ExitSecurityException stack trace
Thanks to Petr Nejedly and Jesse Glick the problem was identified and fixed. When jemmy event queue is installed, IDE exit is dispatched through this untrusted queue and IDE security manager refuses it to exit. In order to fix it the TopSecurityManager.exit call was re-plan to RequestProcessor. Checking in org/netbeans/core/NbTopManager.java; /cvs/core/src/org/netbeans/core/NbTopManager.java,v <-- NbTopManager.java new revision: 1.197; previous revision: 1.196
Verified with 200311241900.
*** Issue 32002 has been marked as a duplicate of this issue. ***