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.
Initialization of SwingBrowser leads to deadlock, see attachment. How to reproduce: - use latest jdk1.6 - Start Netbeans NB6.0, dev build with JDK's option java.net.useSystemProxies=true - open Options dialog => deadlock appears. On my configuration 100% reproducible. ============================================ Product Version = NetBeans IDE Dev (Build 200611131900) Operating System = Linux version 2.6.15-27-386 running on i386 Java; VM; Vendor; Home = 1.6.0-rc; Java HotSpot(TM) Client VM 1.6.0-rc-b104; Sun Microsystems Inc.; /space/shared/java/jdk1.6.0/jre System Locale; Encoding = us (nb); UTF-8
Created attachment 36109 [details] deadlock
At least once I was to reproduce. Another attempt resulted in crashed JVM (open swing browser, then open options window).
I filed bug against JDK - 6496491. It is not clear if we can fix it in NetBeans. Successfully reproduced on my Ultra-20 w/ FC4 64-bit and Petr Nejedly's machine.
two ways how to avoid this: 1.) Use ORBit2 >= 2.14.2 gnome-vfs >= 2.16.1 libraries. 2.) Invoke java.net API on the same thread as Desktop API
the third one: disable use of java.awt.Desktop on Linux/Solaris if the property is set. /shared/data/ccvs/repository/extbrowser/src/org/netbeans/modules/extbrowser/SystemDefaultBrowser.java,v <-- SystemDefaultBrowser.java new revision: 1.9; previous revision: 1.8 Too agressive for those who have recent GNOME libs and does not cover the case if you edit this preference in jre/lib/net.properties. I'll track the bug in JDK and reenable this for JDK where it gets fixed.