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: | Deadlock on evaluating expresion with endless loop | ||
---|---|---|---|
Product: | debugger | Reporter: | pzajac <pzajac> |
Component: | Java | Assignee: | issues@debugger <issues> |
Status: | CLOSED DUPLICATE | ||
Severity: | blocker | CC: | jchalupa |
Priority: | P3 | Keywords: | THREAD |
Version: | 4.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
threads dump
threads dump |
Description
pzajac
2004-11-01 09:57:39 UTC
Created attachment 18634 [details]
threads dump
*** This issue has been marked as a duplicate of 46614 *** v According to comment by Hanz in issue 46614, this issue is not duplicate. Current solution is not flawless. 1, Create a static method containing endless loop 2, Add expression to watches which will invoke the method 3, Start debugging -> when debugger evaluates the expression, the IDE is not locked any more, but becomes very unresponsive - all the actions lasts long time. BTW this work fine in other IDEs. Sorry, but onece again. This is not a deadlock. If you think its real user problem, create a new issue for it. But I think that its user problem. The watch with infinite loop doesn't block debugger. But after finish debugger action the AWT-QUEUE is blocked again. Threads dump is in the attachment. Created attachment 20582 [details]
threads dump
*** This issue has been marked as a duplicate of 56233 *** v |