You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…ompletion
**Bug**
We currently pause on the last line of a program. Node 6 made some change and now does not respond to debug messages sent after this pause.
**Fix**
This change has two fixes:
* Add an explicit timeout when removing breakpoints. We have an identical timeout when adding breakpoints so it probably makes sense to add this.
* On our low level send calls, register the cancellation token to cancel the promise.
A better fix would be just to never send requests to node after we run to the last line, but it is not clear how we can detect this without a wrapper. The debug protocol does not seem to emit any events about this and the app is offically still running.
closesmicrosoft#935
mjbvz
changed the title
Hang on Remove Breakpoint in Node 6.1.0
Hang on Remove Breakpoint after program completes
May 25, 2016
Repo
Expected
Breakpoint is removed
Actual
Infinite hang.
On Node 5.x, this operation is canceled out after a few seconds and we can continue on, but with Node 6.1.0 we hang forever. The hang is on this line: https://github.com/Microsoft/nodejstools/blob/master/Nodejs/Product/Nodejs/Debugger/DebugEngine/AD7BoundBreakpoint.cs#L52
The text was updated successfully, but these errors were encountered: