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.
Created attachment 99782 [details] thread dump Steps: - open 2 forms - try to copy some components from one form to the other => deadlock Product Version: NetBeans IDE Dev (Build 100602-82847c70b11c) Java: 1.6.0_20; Java HotSpot(TM) 64-Bit Server VM 16.3-b01 System: Linux version 2.6.32-22-generic running on amd64; UTF-8; cs_CZ (nb)
This issue is another consequence of J.Tulach's incompatible change in PropertySheet's threading model, see issue 168744. getPropertySets() used to be called (by PropertySheet) in event-dispatch thread only. Now it is called also in other threads. Accessible.getAccessibleContext() is called during creation of properties/property sets to determine whether the component should have accessibility properties. Unfortunately, JTextField.getAccessibleContext() accesses UI resources (it attempts to grab java.awt.Component$AWTTreeLock). Hence, it shouldn't be called outside AWT thread.
Yesterday, I saw this deadlock, too (on Windows) => changing Platform to All/All.
Isn't it a good candidate for NB 6.9.1?
Fixed. Modified file: http://hg.netbeans.org/cdev/rev/c0e08a2fe58d > Isn't it a good candidate for NB 6.9.1? There is a whole series of problems caused by J.Tulach's fix of issue 168744. See, for example, issues 186528, 186191, 186746, 186375. We have to make sure that this area settles down before we port it to NB 6.9.1.
*** Bug 187295 has been marked as a duplicate of this bug. ***