Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using CTRL+C can cause break of debugging

See original GitHub issue

I’ve been working with VSCode for a while and I often catch myself on pressing F5, noticing an error and I press CTRL+C multiple times to quickly terminate. I noticed that sometimes VS Code will come back from this but in a broken state where pressing F5 doesn’t do anything anymore. This may or may not be related to me pressing it during Formatting on Save but maybe overall canceling running may impact how VSCode processes it. Of course maybe I shouldn’t cancel things like I do … but well… trigger happy it is.

Issue Analytics

State:
Created 5 years ago
Comments:10 (6 by maintainers)

Top GitHub Comments

1reaction

rjmholtcommented, Oct 18, 2018

@PrzemyslawKlys if you take a normal PowerShell console session, can you cancel connecting to office365 in the middle of things? Or is it just faster?

<kbd>Ctrl</kbd>+<kbd>C</kbd> can only cancel when PowerShell gets the opportunity to. So if it’s a .NET call, or there’s some thread scheduling to wait on, it can’t work. I suspect it might be the latter case here.

0reactions

PrzemyslawKlyscommented, Oct 22, 2018

Also I see the issue with showing .json was solved in VSCode? Maybe this affects how things work?