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.
[NetBeans 6.5M1, Build 200806270102, JDK 1.6.0] This was found when testing http://wiki.netbeans.org/TS_61_RubyDebugger Ruby Debugger - Section 6. I don't know yet how to reproduce the bug, but it was encountered 5 times during 30 minutes of testing. 1) Have a new Ruby project with main.rb (and breakpoint) like following: def fib(n) if n<2 then return n else return fib(n-1) + fib(n-2) end end 5.times do |i| puts fib(i) #BREAKPOINT HERE end 2) Debug this file on Built-in JRuby 1.1.2 (though this may also be an issue with Ruby platform, I was unable to reproduce it there) ERROR: The debugging suddenly ends (toolbar returns to standart, no debug session visible), but the debugger task is still running, and cannot be terminated by usual means (status bar). This can happen on its own, even when no user input is taking place. (Thread dump attached) NOTE: If you try to close the task via the status bar, you get only following console output: WARNING [org.netbeans.modules.ruby.debugger.Util]: Finish is not supposed to be called when a process is already terminated NOTE: All the freezed processes are listed as not terminated when exiting IDE Sorry I couldn't give a better info about this.
Created attachment 63581 [details] ThreadDump after debug task freeze
UPDATE: It seems the tasks kept running even after closing IDE, so I had to manually kill many java.exe processes. This also prevented main.rb files from being deleted.
You mean that after you started debugger it does not stop on the breakpoint and you was not able to kill it? Or did it stop on the breakpoint and after you press F5 (cont) few times it did not finished? Need more info here, I'm not able to reproduce. Thanks.
Will try to. This happened randomly during the test of Step In, Step Out, Step Over and Step to Cursor behavior. Even without any input from me (just watching the screen for a while), the debugging suddenly ended, IDE switched back to standart edit mode, but the task remained. It's hard to reproduce, but I reported anyway mainly do to quite serious consequences (hundreds of MB ram occupied until system reboot/manual kill). The good news is that Issue 138462 is fully reproducible (for me) and seem to cause exactly the same behavior (among other errors)
Might be caused by 'step out' which seems to be broken. I need to fix issue 138307 in the first place which seems to cause a lot of discrepancies.
Issue #138462 was fixed. And there are no duplicates of this one. Might be related to issue 138462. Please reopen, if you are able to reproduce again.