Debugger stops responding after a bit of debugging with watches defined

[rkeithhill]

VS Code 1.8.1, PowerShell ext 0.9.0, Windows 10 AU.

I'm finding that if I have any watch defined, the debugger becomes unresponsive after hitting a few breakpoints. I didn't see anything obvious in the log file.

1485651267-212b9958-570a-4602-8228-df639d9e79441485647668037.zip

[kapilmb]

@rkeithhill Can you please provide me some snippet that I can use to reproduce this issue?

[rkeithhill]

It is easy to repro. Open up the Examples folder. Open DebugTest.ps1 and set a line breakpoint on the line $i = $i + 1. Add a watch for $i. Select the PowerShell Launch (current file) and press F5. After the breakpoint is hit, press F5 to resume and the debugger never comes back. Try starting the debugger again, and it is wedged.

[kapilmb]

Thanks @rkeithhill

[daviwil]

Looks like this was fixed in last Friday's Insider build, they don't send watch requests after the debugger resumes any longer. I've got my own simple fix for the issue in the meantime, will add it to my PR.