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.
This deadlock is hard to reproduce. It occures after long work of automated tests. In the attachment there are 3 Full Thread Dumps. Last time it happened when all automated tests finished and I did these actions: Expand some filesystem node in the Explorer. ERROR - Explorer did not show any sub node of this filesystem although in the directory there was some files. Close Source Editor window. ERROR - Deadlock occured
Created attachment 3615 [details] 1.
Created attachment 3616 [details] 2.
Created attachment 3618 [details] 3. - Last occurence
Racecondition in IDLDataObject causes DeadLock of the whole IDE. So, the priority changed to P2.
The deadlock is caused due to fileChanged after the parse thread changed the status of data object to STATUS_OK || STATUS_ERROR and before the wainting thread in the method getPossibleNames reads the value of status. This scenerio causes lost of the notification.
Fixed by removing the invalid state from the IDLDataObject.
Verified - No deadlock occured for a long time.
Resolved for 3.3.x or earlier, no new info since then -> closing.