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.
I am running 1.5.0_03 EA and I get following deadlock any time I want, but also all the time when I do not want to see it at all. I am just debuggging netbeans with a breakpoint in Children.setEntries after adding new file into java package. After few steps it deadlocks and I have to kill the ide, the debugee and start from scratch. Pretty annoying.
I can not reproduce it on WinXP JDK1.5.0_01. Can you attach thread dump stack, please?
Created attachment 20711 [details] Sorry I must have forget to attach the file
Created attachment 20750 [details] New deadlock, now on 1.4.2_05-b04
I have this.this$0.getClass() among watches and after few step over, the debugger stopped, I had to use "Pause" to show me the PC and as soon as I used step over again, I got the deadlock.
Created attachment 20928 [details] I've got similar situation while leaving the ide to play ping pong
I think I the d.txt actually tells good news. The debugger was locked (I could not do f8, f7, ctrl+f5, etc.), but the UI was funtional and if similar behaviour works everytime the debuggee gets to problems, this is not p1 anymore. I could not get thread dump from debuggee, xtest killed it instead. sorry.
Debugger could be stopped now without impact on the rest of the IDE --> downgrading to P3
Not reproducible after synchronization changes (org.netbeans.modules.debugger.jpda.JPDADebuggerImpl, org.netbeans.api.debugger.ActionsManager)
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.