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.
Summary: | Ruby debug task freezing | ||
---|---|---|---|
Product: | ruby | Reporter: | polan <polan> |
Component: | Debugger | Assignee: | Martin Krauskopf <mkrauskopf> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | Windows Vista | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | ThreadDump after debug task freeze |
Description
polan
2008-06-27 09:39:02 UTC
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. 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) 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. |