OmniSharp.exe uses 10 GB RAM and 50% CPU
See original GitHub issueEnvironment data
dotnet --info
output:
.NET Command Line Tools (2.1.4)
Product Information:
Version: 2.1.4
Commit SHA-1 hash: 5e8add2190
Runtime Environment:
OS Name: Windows
OS Version: 10.0.15063
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.4\
Microsoft .NET Core Shared Framework Host
Version : 2.0.5
Build : 17373eb129b3b05aa18ece963f8795d65ef8ea54
VS Code version: 1.20.1 C# Extension version: 1.14
Steps to reproduce
Edit C# code with Visual Studio Code
Expected behavior
Low CPU and RAM usage
Actual behavior
Unacceptable
Issue Analytics
- State:
- Created 6 years ago
- Reactions:10
- Comments:26
Top Results From Across the Web
OmniSharp using tons of memory while using Rider
OmniSharp.exe uses 10 GB RAM and 50% CPU I'm not using VSCode for C# programming, what do I need to do to correctly...
Read more >1gb ram usage OMNISHARP and 800MB VSCODE ! 1.9gb in ...
Yeah, I've started seeing this recently too. Not sure if it's just the project I'm working on but I suspect it's an update....
Read more >Why does VS Code require so much memory? How can I ...
Opening VS Code is like opening another Chrome window, it uses a lot of RAM, and CPU. Neovim uses around 10 mbs of...
Read more >Visual Studio 2022 - Microsoft Developer Blogs
(video showing devenv.exe taking 5 GB of memory…) ... I wish Microsoft would enhance the High-DPI support in Windows.
Read more >Administration Guide Red Hat CodeReady Workspaces 2.1
The sum of the expected memory consumed by all the components launched by the ... If Omnisharp.exe is running, it logs all information...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Did some more testing, it seems like the culprit in my case is the Async Completion. Disabled it and the usage is more reasonable.
In the settings of the C# extension, there’s a option called “[BETA] Async completion.” or something like that.