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 127924 [details] Threa dump Netigso notification events are posted to RequestProcessor which can lead to deadlock. 1. When creating a subclass of a thread, security manager is doing some check that getContextClassLoader method is not overridden in subclass. This leads to extensive class loading which ends up with bundleChanged notification which is processed by RequestProcessor. All the processing is running under auditSubclass (SoftCache) lock. 2. When any other thread is trying to post its task to RequestProcessor and there is no thread in a pool available, the Processor thread instance creation can lock with the first one. (1.) See attached thread dump for details.
ergonomics#d9b7bba1e24e
Integrated into 'main-golden', will be available in build *201211211016* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/d9b7bba1e24e User: Jaroslav Tulach <jtulach@netbeans.org> Log: #222258: Netigso notification events can lead to deadlock #222258: Don't hold internal lock when constructing new Processor