Debug session reports timeout after 10000 ms.

[mverbaas]

Issue Type: Bug

After debug sessions ends, it errors out with "timeout after 10000 ms" message and doesn't close the debug controls.

Extension version: 2020.6.0
VS Code version: Code 1.47.2 (17299e413d5590b14ab0340ea477cdd86ff13daf, 2020-07-15T18:22:06.216Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item	Value
CPUs	Intel(R) Xeon(R) CPU E5-2667 v4 @ 3.20GHz (4 x 3196)
GPU Status	2d_canvas: unavailable_software flash_3d: disabled_software flash_stage3d: disabled_software flash_stage3d_baseline: disabled_software gpu_compositing: disabled_software multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: disabled_off rasterization: disabled_software skia_renderer: disabled_off_ok video_decode: disabled_software viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off_ok webgl: unavailable_software webgl2: unavailable_software
Load (avg)	undefined
Memory (System)	16.00GB (8.91GB free)
Process Argv
Screen Reader	no
VM	100%

[SydneyhSmith]

Thanks @mverbaas for opening this issue, it would be great it you could provide a bit more context around what you were doing/what vscode looked like when this happened (screen shots and gifs are great!) it would be really helpful if you could also attach the logs--instructions for how to do that are here

[mverbaas]

Hi @SydneyhSmith, sorry for the lack of the data. Hope this attachment contains some leads.
github#2821.zip

[SenseiJoe]

I see the same issue debugging powershell scripts. It happens often when sitting at a breakpoint for a bit.

[SydneyhSmith]

Thanks for all the additional information, are you experiencing any issues beyond the strange notification...or if you just ignore the notification are you otherwise able to perform your desired tasks.

Looks like a race condition within the debugger between cleaning up the pipe, and responding to that message.

[SenseiJoe]

Ya, I just ignore it, click through it. It restarts without an issue.

[mverbaas]

I just stop the debugger at the top (for me) and can continue without any noticeable effects.