VSCode stops processing 'Start Debugging'

[PrzemyslawKlys]

Issue Description

I am experiencing a problem with... F5 ('Start Debugging') stopping to work very often. Last few weeks it has been stopping all the time. I am not sure if the logs are of any help thou. I have to restart PowerShell session or use F8.

Attached Logs

Follow the instructions in the README about
capturing and sending logs.

1568380290-e5000958-344d-442c-be6c-5a263b8675e61568354258606.zip

Environment Information

Visual Studio Code

Name	Version
Operating System	Windows_NT x64 10.0.18362
VSCode	1.38.1
PowerShell Extension Version	2019.5.0

PowerShell Information

Name	Value
PSVersion	5.1.18362.145
PSEdition	Desktop
PSCompatibleVersions	1.0 2.0 3.0 4.0 5.0 5.1.18362.145
BuildVersion	10.0.18362.145
CLRVersion	4.0.30319.42000
WSManStackVersion	3.0
PSRemotingProtocolVersion	2.3
SerializationVersion	1.1.0.1

Visual Studio Code Extensions

Visual Studio Code Extensions(Click to Expand)

Extension	Author	Version
auto-rename-tag	formulahendry	0.1.0
beautify	HookyQR	1.5.0
bracket-pair-colorizer-2	CoenraadS	0.0.28
code-settings-sync	Shan	3.4.2
gitlens	eamodio	9.9.3
html-css-class-completion	Zignd	1.19.0
live-html-previewer	hdg	0.3.0
markdown-all-in-one	yzhang	2.4.2
markdown-preview-enhanced	shd101wyy	0.4.3
markdown-shortcuts	mdickin	0.11.0
material-icon-theme	PKief	3.9.0
powershell	ms-vscode	2019.5.0
project-manager	alefragnani	10.7.0
theme-monokai-pro-vscode	monokai	1.1.14
vscode-html-css	ecmel	0.2.3
vscode-wakatime	WakaTime	2.2.0
xml	DotJoshJohnson	2.5.0

[rjmholt]

Thanks for opening an issue @PrzemyslawKlys. Can I ask what you mean by "stopping" here? Would you be able to attach a GIF maybe of the process occurring? Is it a crash, or is debugging just ending unexpectedly? Or is it hanging?

There's a strange sequence I've observed in some logs recently where VSCode sends us a debugger shutdown message. It's likely in response to something we do, but it's a new change in VSCode and we haven't worked out what's going on there yet.

[PrzemyslawKlys]

Generally it works in a way where I press F5 wait for script to finish, fix something, run again and again and randomly (sometimes after 2 minutes, sometimes after 2 hours) F5 just stops responding. Nothing is happening when pressed. You have to restart session to continue. But it's not crashed. Just not responding. To me it looks like I pressed F5 and it did register it and started executing in the background but it didn't inform the GUI and at that point The debug session is running on it's own. But that’s just a noob guess.

[rjmholt]

To me it looks like I pressed F5 and it did register it and started executing in the background but it didn't inform the GUI and at that point The debug session is running on it's own

Yeah that sounds familiar. Well @TylerLeonhardt's been working hard on some big changes here, so we should have something new to try in the next few weeks hopefully.

[westerdaled]

I am also getting affected by this issue again; resulting in frequent "nostalgic" use of the ISE 😯

Is there a min version of PowerShell 5 we should be using?
`
ame Value

---

PSVersion 5.1.18362.145
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.18362.145
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
`

[TylerLeonhardt]

PowerShell 5.1 should work. What version of the .NET Framework do you have installed just so we know?

The next preview extension release will have the refactor that @rjmholt mentioned. I'd love to hear what you folks have to say when that drops.

[PrzemyslawKlys]

I can give it a go, however if it will have problems with PSReadline it's a bit useless.

[westerdaled]

PowerShell 5.1 should work. What version of the .NET Framework do you have installed just so we know?

The next preview extension release will have the refactor that @rjmholt mentioned. I'd love to hear what you folks have to say when that drops.

regedit HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\1033 it show for Release key: 528040 which is .NET framework 4.8 ( probably through windows update) . I am happy to test the refactor ( hopefully PSReadline support is stable) . At the end of the day I just want to get to the bottom of the debug "suspended animation" I like others seem to be experiencing

[rjmholt]

Ok just took a look through the logs again and it's not clear just yet what the issue is. We're hoping to get the new version of debugging stack out soon as a preview release (it's just waiting on some upstream logging work so we can find bugs better) so when that's out it may well solve this issue