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.
[ BUILD # : 6.5 RC1 ] [ JDK VERSION : 1.6.0_07 ] When I first started 6.5 RC1 after installation the editor locked completely when I pressed the Open Project toolbar button. I started visualvm and noticed the Swing-Shell thread was blocked. I killed the process using task manager (windows) and restarted NetBeans. This time it worked fine. "Swing-Shell" daemon prio=6 tid=0x03f37400 nid=0x1740 waiting for monitor entry [0x2eb8f000..0x2eb8fc14] java.lang.Thread.State: BLOCKED (on object monitor) at sun.awt.shell.Win32ShellFolder2.isLink(Win32ShellFolder2.java:736) - waiting to lock <0x09ba4c88> (a sun.awt.shell.Win32ShellFolder2) at sun.awt.shell.Win32ShellFolder2$10.call(Win32ShellFolder2.java:651) at sun.awt.shell.Win32ShellFolder2$10.call(Win32ShellFolder2.java:643) at sun.awt.shell.Win32ShellFolderManager2$ComInvoker.invoke(Win32ShellFol derManager2.java:491) at sun.awt.shell.Win32ShellFolder2.listFiles(Win32ShellFolder2.java:643) at javax.swing.filechooser.FileSystemView.getFiles(FileSystemView.java:43 4) at javax.swing.plaf.basic.BasicDirectoryModel$LoadFilesThread$1.call(Basi cDirectoryModel.java:225) at javax.swing.plaf.basic.BasicDirectoryModel$LoadFilesThread$1.call(Basi cDirectoryModel.java:221) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu tor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. java:907) at sun.awt.shell.Win32ShellFolderManager2$ComInvoker$3.run(Win32ShellFold erManager2.java:458) at java.lang.Thread.run(Thread.java:619) Locked ownable synchronizers: - <0x09bb1d10> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
Created attachment 72431 [details] Thread dump output from visualvm
reassign to core for evaluation
Dafe, have you already had a chance to look at this? Thanks!
closing as wontfix because it is JDK problem. Nothing can be done on NB side :( The bug has been accepted by JDK team. Hopefully will be fixed in next JDKs updates http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6744953