IntelliSense slow or unresponsive forced to kill powershell to force it to work.

[ebmarquez]

System Details

• Operating system name and version:

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.16299.0 Microsoft Windows NT 10.0.16299.0

• VS Code version: 1.21.1
• PowerShell extension version: 1.6.0
• Output from $PSVersionTable:

Name                           Value
----                           -----
PSVersion                      5.1.16299.251
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.16299.251
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Copy / paste the following commands into the PowerShell Integrated Console, and paste the output here:

code -v

1.21.1
79b44aa704ce542d8ca4a3cc44cfca566e7720f1
x64

$pseditor.EditorServicesVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
1      6      0      0

code --list-extensions --show-versions

codezombiech.gitignore@0.5.0
donjayamanne.githistory@0.4.0
DotJoshJohnson.xml@1.9.2
eamodio.gitlens@8.2.0
formulahendry.docker-explorer@0.1.6
mohsen1.prettify-json@0.0.3
ms-python.python@2018.3.1
ms-vscode.PowerShell@1.6.0
ms-vsliveshare.vsliveshare@0.2.307
njpwerner.autodocstring@0.2.0
PeterJausovec.vscode-docker@0.0.26
ryu1kn.partial-diff@0.5.1
tushortz.python-extended-snippets@0.0.1
vscoss.vscode-ansible@0.1.5
wholroyd.jinja@0.0.8

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.16299.251
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.16299.251
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

### Issue Description
IntelliSense is slow or unresponsive when using powershell in the editor.  
To get it to work correctly again, I have to kill and restart powershell in Vscode to force it to work again.

### Attached Logs

logs.zip

[TylerLeonhardt]

Hi there, thanks for the report. Can you please attach the logs (instructions: https://github.com/powershell/vscode-powershell#2-capture-verbose-logs-and-send-them-to-us)

And also give me some details on how big your workspace is and how big your file is that's giving you slow intellisense?

[ebmarquez]

it shows the logs are already attached.
logs.zip
My PSM1 file is 6704 lines

workspace size
All files which includes Jinja2, C#, Python, Powershell:

(Get-ChildItem .\DeploymentToolKit\ -Recurse).count
7914

Powershell related files:

((Get-ChildItem .\DeploymentToolKit\ -Recurse -Filter "*.ps?1").FullName).count
38

[lushibi]

I have a problem that the intellisense does not work at all, until I exit the "PowerShell Integrated Console" which is opened by vscode automatically.

I confirm the behaviour, killing the Integrated Console in VSCode made the IntelliSense work back again.

It seems that the following "old" line in my user settings was messing up things.
"powershell.powerShellExePath": "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe"

Once removed, IntelliSense is working fine and quickly again.

[TylerLeonhardt]

@ebmarquez oops missed the logs. Thanks for the extra info!

[TylerLeonhardt]

This is one of the more important perf bugs that I've been hearing about.

[rayholtz]

I also can confirm that killing the Powershell Integrated Console makes Intellisense work again. I have VScode v1.22.1.

[ChrisLynchHPE]

Yes, killing the PIC does make Intellisense "work" again. However, really need variable and function lookup Intellisense provides when the PowerShell session is running. I really hope performance can dramatically improve.

Data points about my dev system:

[PS] ...\MyDir> code -v
1.23.1
d0182c3417d225529c6d5ad24b7572815d0de9ac
x64
[PS] ...\MyDir> $pseditor.EditorServicesVersion
[PS] ...\MyDir> code --list-extensions --show-versions
alefragnani.Bookmarks@0.19.1
alefragnani.pascal@0.11.0
humao.rest-client@0.18.4
idleberg.innosetup@1.0.3
mechatroner.rainbow-csv@0.3.0
mohsen1.prettify-json@0.0.3
ms-python.python@2018.4.0
ms-vscode.csharp@1.15.2
ms-vscode.github-issues-prs@0.9.0
ms-vscode.PowerShell@1.7.0
robertohuertasm.vscode-icons@7.23.0
Shan.code-settings-sync@2.9.2
tariky.easy-snippet-maker@0.0.6
tht13.html-preview-vscode@0.1.1
wayou.vscode-todo-highlight@0.5.12
[PS] ...\MyDir> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.17134.81
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17134.81
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Also, my workspace includes both a PowerShell module (1 PSM1) and a C# library. The PSM1 is ~2.8MB, and contains 33585 lines (~45% of those lines are blank).

[cpdohert]

code -v

1.25.1
1dfc5e557209371715f655691b1235b6b26a06be
x64

$pseditor.EditorServicesVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
1      8      2      0

code --list-extensions --show-versions

ms-azuretools.vscode-cosmosdb@0.8.0
ms-vscode.azure-account@0.4.3
ms-vscode.PowerShell@1.8.2
ryu1kn.partial-diff@1.3.0

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.17134.165
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17134.165
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

I was having this problem consistently and found a possible cause.

I was developing a PowerShell Module for internal use. An old version of the module which I'd forgotten about was installed in C:\Users\cpdohert\Documents\WindowsPowerShell\Modules\MyModule\MyModule.psm1

I was also regularly running Import-Module C:\Users\cpdohert\Documents\repos\MyModule\MyModule.psm1 -Force in a PowerShell ISE window outside VS Code.

When I deleted the old C:\Users\cpdohert\Documents\WindowsPowerShell\Modules\MyModule\MyModule.psm1 file, IntelliSense began working speedily again.

Also, the slowdown only occurred once I upgraded to 1.8.2. Under 1.8.1 this configuration did not cause any problems.

[OneSpecialPeg]

Experiencing the same issues. Killing the terminal resolved the issue for me but I don't have old modules or packages.

[rjmholt]

Two things that you can try for now are:

• disabling CodeLens
• disabling ScriptAnalysis

We've been chipping away at performance issues recently, although there's still a lot of work to be done. But hopefully you'll experience some improvement in the next release. Here are the recent PRs:

• Remove unnecessary LINQ calls from LanguageServer PowerShellEditorServices#743
• Remove LINQ usage in language service methods PowerShellEditorServices#737
• Cache the reflection call done for completions PowerShellEditorServices#736
• Fix codelens crash when a file does not exist PowerShellEditorServices#732
• Reduce allocations in the CodeLens providers PowerShellEditorServices#719
• Reduce allocations when parsing files PowerShellEditorServices#715

The bigger performance gains are ones that require either changes in PSScriptAnalyzer or architectural changes in EditorServices, so we've been trying to fix those the "right" way, trying not to break too much.