IntelliSense is occasionally slow when editing PowerShell scripts

[tibmeister]

At times it could take up to 90 seconds for Intellisense to finally come up, sometimes I have to manually initiate (Ctrl+Space), and other times it comes up very quickly.

System Details

• Operating system name and version: Wind 10 Enterprise x64, 8 CPU, 12GB RAM
• VS Code version: 1.10.2
• PowerShell extension version: v0.11.0
• Output from $PSVersionTable:

Name Value

---

PSVersion 5.0.10586.672
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.10586.672
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

[daviwil]

Is it slow after working in a session for a while or only at the very beginning?

[daviwil]

Hey Jody, when you see this issue again, can you evaluate the $Error variable in your session and paste the output here?

[tibmeister]

Sorry, been a crazy couple of days. I can't seem to find a pattern as to when this happens, but I will keep a bit more attention to it.
I will look for the $Error to see if anything shows up, but I think that since it does eventually show up if I'm patient, it's more of a performance issue.

[daviwil]

No problem! One more thing to try when you see this again, when IntelliSense becomes slow, try running these two commands in the Integrated Console and then try IntelliSense again to see if the speed improves:

Remove-Module PowerShellGet -Force
Remove-Module PackageManagement -Force

This takes those two modules out of the session. I suspect that they may be causing the IntelliSense slowness.

[daviwil]

Linking this to an issue I created against the PackageManagement module since that is definitively the cause of this issue:

OneGet/oneget#275

[dotps1]

intellisense for the PowerShellGet module is slow even in the regular shell.

[daviwil]

Yeah, that's because PowerShellGet loads PackageManagement, so loading either causes the slowdown.