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 154178 [details] Project containing a class launching two deadlocked threads. Product Version: NetBeans IDE Dev (Build 201506110001) Java: 1.7.0_76; Java HotSpot(TM) 64-Bit Server VM 24.76-b04 Runtime: Java(TM) SE Runtime Environment 1.7.0_76-b13 System: Linux version 3.13.0-37-generic running on amd64; UTF-8; cs_CZ (nb) Description: ============ Detection of deadlock does not work for the first time. If user finishes the debugging session and starts another one, deadlock detection works normally. Steps to reproduce: =================== 1. Open attached DeadlockTest project in NetBeans IDE. 2. Press Ctrl+F5 to start debugging session. 3. Once debugging session is started and you see both "Thread-0" and "Thread-1" threads running in "Debugging" view, right click the area and invoke "Check for Deadlock" action from popup menu. Expected: In total 6 different threads are suspended with "Thread-0" and "Thread-1" threads expanded and highlighted in red. Yellow bar is displayed with "Deadlock detected" warning. Actual: Nothing happens. If you Shift+F5 and Ctrl+F5 the project again and repeat step 3, the same deadlock will be detected without problems.
Reproduced and fixed by 289148:435650634b0b http://hg.netbeans.org/core-main/rev/435650634b0b
Integrated into 'main-silver', will be available in build *201506260309* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/435650634b0b User: mentlicher@netbeans.org Log: #252945: Assure that the actions work in tree views as well.
Product Version: NetBeans IDE Dev (Build 201507170001) Java: 1.8.0_51; Java HotSpot(TM) 64-Bit Server VM 25.51-b03 Runtime: Java(TM) SE Runtime Environment 1.8.0_51-b16 System: Linux version 3.13.0-37-generic running on amd64; UTF-8; cs_CZ (nb) Verified. Thanks for the fix.