Language Features still stops working after a while and never recovers

[PrzemyslawKlys]

Issue Description

I am experiencing a problem with...IntelliSense not working after a while.

I am aware of a recent fix and other closed issues:

• Intellisense Hanging in Editor #2590
• Auto-completion fails due to performance issues #2522
• PowerShell Intellisense and most right-click features stop working #2596

But I still experience issues, far less but still.

Attached Logs

1586591887-8aec1d54-a22f-4e9a-9d5a-026cf95b0ba11586539769772.zip

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

Environment Information

Visual Studio Code

Name	Version
Operating System	Windows_NT x64 10.0.18363
VSCode	1.44.0
PowerShell Extension Version	2020.4.1

PowerShell Information

Name	Value
PSVersion	5.1.18362.752
PSEdition	Desktop
PSCompatibleVersions	1.0 2.0 3.0 4.0 5.0 5.1.18362.752
BuildVersion	10.0.18362.752
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
autoit	Damien	1.0.4
beautify	HookyQR	1.5.0
bracket-pair-colorizer-2	CoenraadS	0.0.29
code-settings-sync	Shan	3.4.3
codesnap	adpyke	1.0.27
excel-to-markdown-table	csholmq	1.2.2
gistfs	vsls-contrib	0.0.65
github-linker	gimenete	0.2.3
gitlens	eamodio	10.2.1
html-preview-vscode	george-alisson	0.2.5
markdown-all-in-one	yzhang	2.8.0
markdown-preview-enhanced	shd101wyy	0.5.2
markdown-shortcuts	mdickin	0.12.0
material-icon-theme	PKief	4.0.1
pdf	tomoki1207	0.5.1
powershell-preview	ms-vscode	2020.4.1
project-manager	alefragnani	10.11.0
reg	ionutvmi	1.0.1
theme-monokai-pro-vscode	monokai	1.1.15
vscode-html-css	ecmel	0.2.3
vscode-markdownlint	DavidAnson	0.34.0
vscode-pull-request-github	GitHub	0.15.0
vscode-toggle-quotes	BriteSnow	0.3.2
vscode-versionlens	pflannery	0.25.0
vscode-wakatime	WakaTime	4.0.0
vscode-yaml	redhat	0.7.2
xml	DotJoshJohnson	2.5.0

[TylerLeonhardt]

Honestly, at this point, the problem has to be deep in PowerShell Editor Services's handling of the PowerShell runspace.

I've tried to avoid diving into that as it will take a lot of time and will involve coordinating with @daxian-dbw on PSReadLine but unfortunately that's where we're at.

I'll need more people to bother @SteveL-MSFT here and on Twitter to treat this as a priority.

[mrboring]

@TylerLeonhardt I experienced this once yesterday. I commented here as #2522 is now closed.

[daxian-dbw]

I also experienced the same with PowerShell extension 2020.3.0 with PowerShell 7.0.

Basically, intellisense stops working after a while. Then, if you run a command in the integrated console, it doesn’t get executed, but instead the command prompt will be displayed immediately, and after that things starts to work again. But the same will happen after a while again.

[PrzemyslawKlys]

Maybe related: #2364

[TylerLeonhardt]

@daxian-dbw the Preview extention has a bunch of work in it to prevent this... But this issue claims it isn't completely fixed.

[rkeithhill]

I'm seeing a similar issue and I never started a debug session. I'm on preview 2020.4.2 (VSCode 1.44.2) and here's my log zip. I'm not seeing anything obvious here. BTW it is cool that cancel requests indicate the message number they're cancelling. I just wish the original LSP msgs displayed their request number.
EditorServices.zip

[rkeithhill]

OK, my PSIC is completely unresponsive which would explain why completions aren't working. :-) Now, why is PSIC wedged?