PowerShell / PowerShell/PowerShellEditorServices
Unreasonably enormous memory usage with Kate on Windows since 3.8
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 767
- Forks
- 266
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Steps to reproduce
I don't know what exactly triggers this and narrowing it down isn't easy, but here's some possible steps:
- Install Kate 23.08 on x64 Windows, using traditional installation.
- Unpack PowerShellEditorServices somewhere convenient.
- Create a PowerShell script like this:
mkdir -ErrorAction SilentlyContinue $env:TEMP/pses-qdls
& 'C:/PATH/TO/PSES/PowerShellEditorServices/Start-EditorServices.ps1' -BundledModulesPath C:/PATH/TO/PSES -LogPath $env:TEMP/pses-qdls/logs.log -SessionDetailsPath $env:TEMP/pses-qdls/session.json -FeatureFlags @() -AdditionalModules @() -HostName 'qdls' -HostProfileId 'qdls' -HostVersion 0.0.0 -Stdio -LogLevel Normal
- Enable Kate's LSP client: Toggle on Settings > Configure Kate > Plugins > LSP Client, then apply.
- Go to the Settings > Configure Kate > LSP Client > User Server Settings and add a block like this:
{
"servers": {
"powershell": {
"command": ["pwsh", "-NoLogo", "-NoProfile", "-Command", "$PSStyle.OutputRendering = 'PlainText'; & C:/PATH/TO/PowerShellLanguageServer.ps1"],
"highlightingModeRegex": "^PowerShell$"
}
}
}
- Open Task Manager and watch the memory usage of the
pwshprocess Kate spawns as you browse around a large PowerShell project. Make sure you have a build of the project on$PSModulePathso PSES sees its functions etc.
Expected behavior
Reasonable memory usage.
Actual behavior
Memory usage of multiple Gbytes after running for a few minutes.
Error details
No response
Environment data
PS$> $PSVersionTable
Name Value
---- -----
PSVersion 7.3.6
PSEdition Core
GitCommitId 7.3.6
OS Microsoft Windows 10.0.19043
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Version
3.10.0, 3.9.0, 3.8.7; 3.7.3 not affected
Visuals
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the memory growth using Kate, PowerShellEditorServices, Start-EditorServices.ps1, and PowerShellLanguageServer.ps1 while browsing a large project. Compare version 3.7.3 with 3.8.7 and later, then trace the LSP-driven process behavior; done means identifying and correcting the regression so pwsh maintains reasonable memory usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100