PowerShell / PowerShell/vscode-powershell

PSSession is very slow

Open
#1,648 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Extension Terminal Issue-Performance
Dominant language
TypeScript
Stars
1.9k
Forks
547
PR merge metrics
No merged PRs in 30d

Description

Issue Description

Issue Type: Performance Issue

When using powershell (64 or 32) for around 5-10 minutes, running run code snip or debug will result in cpu spikes on powershell, and will hang in the integrated console for multiple minutes, even on a command that runs near real time.

Attached Logs

Log will be emailed.

Environment Information

Visual Studio Code
Name Version
Operating System Windows_NT x64 10.0.17763
VSCode 1.29.1
PowerShell Extension Version 1.10.1
PowerShell Information
Name Value
PSVersion 5.1.17763.134
PSEdition Desktop
PSCompatibleVersions 1.0 2.0 3.0 4.0 5.0 5.1.17763.134
BuildVersion 10.0.17763.134
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
bracket-pair-colorizer-2 CoenraadS 0.0.25
code-settings-sync Shan 3.2.3
eml leighlondon 0.3.1
gc-excelviewer GrapeCity 2.1.26
gitlens eamodio 9.0.3
material-icon-theme PKief 3.6.1
mssql ms-mssql 1.4.0
night-owl sdras 0.4.2
PowerShell ms-vscode 1.10.1
rainbow-csv mechatroner 0.8.0
reg ionutvmi 0.0.2
rest-client humao 0.20.4
sort-lines Tyriar 1.7.0
theme-cobalt2 wesbos 2.1.6
vscode-hasher deerawan 1.0.1
vscode-pull-request-github GitHub 0.2.3
xml DotJoshJohnson 2.3.2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the slowdown in the PowerShell integrated console after 5–10 minutes with the reported VS Code, extension, Windows, and PowerShell versions. Review the attached or emailed logs and compare run-code and debugging behavior; done means the CPU spike and multi-minute hang are no longer reproducible.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, typescript
Domain
devtools, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.