Community
Participate
Working Groups
Latest build I use F5/F6 to step into/over methods & sometimes the debugger goes non- responsive for 10-20 seconds. Cannot easily reproduce but its happened more than a few times lately. Is there a setting which controls timeouts with the target?
Do you see timeout exceptions when this happens? Are you displaying anything complicated in your variables view? logical structures or expensive toStrings ()?
I have seen some timeout exceptions, but most of the time the debugger just becomes non-responsive for 10-20 seconds. I don't believe the variables view shows anything complex. FYI: I open my debugger in its own window if that makes any difference.
Using a different window should not effect anything. If you come across any more specific pointers please let us know. We have seen timeout problems when stepping repeatedly at a "fast" rate that causes the UI to try to update on each step and a logical structure is being viewed in the variables view (bug 94452).
Kent, Have you had anymore trouble with this?
Yes The selected variables do not seem to have much to do with it. All I need to do is hit F6 repeatedly & the debugger disappears for 10 seconds.
Kent, what code are you stepping thru when this happens?
Inside scopes/bindings in the compiler. But of course as I try to reproduce it without any variables selected -> I can't. So maybe it is just a dup of bug 94452
I notice that logical structures can cause delay when stepping (it requires iterative evaluations as you step to create the structure). Were you displaying any logical structures for a map or list?
very likely in some cases. We have our own lookup tables that are used all over the place.
open for investigation, but not committed unless we have a known fix. Could still be a dup of 94452, which we have a potential fix for.
Kent, I think this is a dup of 94452 (see that bug for some updates). What VM are you using? If you are using Sun, can you see if the problem still occurrs on J9?
*** This bug has been marked as a duplicate of 94452 ***
I just had a lengthy delay & there were no variables selected. Does anyone on the Debug team run with the debugger in its own window? If not I suggest you try it for 10 minutes.
FYI: I am debugging JUnit tests launched from a Java perspective... possibly the debugger is waiting for something to update in the other window.
