Omnisharp-vscode: Extension causes high cpu load
- Issue Type:
Performance - Extension Name:
csharp - Extension Version:
1.21.13 - OS Version:
Windows_NT x64 10.0.16299 - VSCode version:
1.42.1
groundsquirrel
All 18 comments
Same here:
Extension: ms-dotnettools.csharp
VSCode version: 1.43.0
Commit: 78a4c91400152c0f27ba4d363eb56d2835f9903a
Date: 2020-03-09T19:44:52.965Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.3.0-7629-generic
jenskalusniak
on 10 Mar 2020
- Issue Type:
Bug - Extension Name:
csharp - Extension Version:
1.21.13 - OS Version:
Windows_NT x64 10.0.18362 - VSCode version:
1.42.1
Grandizer
on 10 Mar 2020
Version: 1.43.0 (user setup)
Commit: 78a4c91400152c0f27ba4d363eb56d2835f9903a
Date: 2020-03-09T19:47:57.235Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
juhoheikkilae
on 10 Mar 2020
- Issue Type:
Bug - Extension Name:
csharp - Extension Version:
1.21.13 - OS Version:
Windows_NT x64 10.0.16299 - VSCode version:
1.43.0
ms-dotnettools.csharp-unresponsive.cpuprofile.txt
The extension is completely unresponsive and useless at the moment. It also seems to prevent other extensions from correctly working which just about makes vs code useless as an IDE.
ahuertabhg
on 11 Mar 2020
Latest version really does seem to tank vscode and break a number of other extensions like gitlens just isn't responsive at all, and vscode cpu% is chewing cores, it also breaks a few other extensions that relied on the old extension name. I've rolled back to the previous version.
XeonG
on 11 Mar 2020
- Issue Type: Bug
- Extension Name: csharp
- Extension Version: 1.21.14
vscode:
- Version: 1.43.0 (user setup)
- Commit: 78a4c91400152c0f27ba4d363eb56d2835f9903a
- Date: 2020-03-09T19:47:57.235Z
- Electron: 7.1.11
- Chrome: 78.0.3904.130
- Node.js: 12.8.1
- V8: 7.8.279.23-electron.0
- OS: Windows_NT x64 10.0.18362
ms-dotnettools.csharp-unresponsive.cpuprofile.txt
When the extension finishes loading, I got the notification: "The extension 'C#' took a very long time to complete its last operation, and it has prevented other extensions from running"
marioquercafe
on 12 Mar 2020
Same issue as reported by the OP
Logs
ms-dotnettools.csharp-unresponsive.cpuprofile.txt
Environment information
VSCode version: 1.44.0
C# Extension: 1.21.14
Dotnet Information
.NET Core SDK (reflecting any global.json):
Version: 3.1.100
Commit: cd82f021f4
Runtime Environment:
OS Name: Windows
OS Version: 10.0.17134
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\3.1.100\
Host (useful for support):
Version: 3.1.0
Commit: 65f04fb6db
.NET Core SDKs installed:
2.1.700 [C:\Program Files\dotnet\sdk]
2.2.301 [C:\Program Files\dotnet\sdk]
3.1.100 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.14 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.14 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.14 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
Visual Studio Code Extensions
|Extension|Author|Version|
|---|---|---|
|csharp|ms-dotnettools|1.21.14|
|team|ms-vsts|1.161.0|
|vim|vscodevim|1.13.0|
|vscode-icons|vscode-icons-team|10.0.0|
|vscode-jest|Orta|3.1.1|;
springbov
on 12 Mar 2020
ms-dotnettools.csharp-unresponsive.cpuprofile.txt
VSCode version: 1.44.0
C# Extension: 1.21.14
Grandizer
on 13 Mar 2020
ms-dotnettools.csharp-unresponsive.cpuprofile.txt
VSCode version: 1.42.1
OS: Windows_NT x64 10.0.17763
C# Extension: 1.21.14
qidydl
on 13 Mar 2020
ms-dotnettools.csharp-unresponsive.cpuprofile.txt
ms-dotnettools.csharp-1.21.14
Version: 1.43.0
Commit: 78a4c91400152c0f27ba4d363eb56d2835f9903a
Date: 2020-03-09T19:34:44.548Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0
frankyjuang
on 13 Mar 2020
ms-dotnettools.csharp-unresponsive.cpuprofile.txt
Same issue. In addition to spiking the CPU, OmniSharp fails to load. This means C# intellisense is currently broken.
EDIT: Intellisense loads after 20 minutes of waiting.
Version: 1.43.0 (user setup)
Commit: 78a4c91400152c0f27ba4d363eb56d2835f9903a
Date: 2020-03-09T19:47:57.235Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
FomTarro
on 14 Mar 2020
Same issue:
Version: 1.44.0-insider (user setup)
Commit: b7bfce30be3c30aa2c33fbe94fe82b81d4105668
Date: 2020-03-17T07:17:39.113Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19587
zendu
on 17 Mar 2020
ms-dotnettools.csharp-unresponsive.cpuprofile.txt
Same issue here.
OmniSharp server started with Mono 6.4.0.
Path: /Users/pc/.vscode/extensions/ms-dotnettools.csharp-1.21.14/.omnisharp/1.34.14/omnisharp/OmniSharp.exe
Version: 1.43.0
Commit: 78a4c91400152c0f27ba4d363eb56d2835f9903a
Date: 2020-03-09T19:34:44.548Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0
jonaspm
on 18 Mar 2020
Please try the v1.21.15 prerelease and let us know if it resolves your performance issue.
JoeRobich
on 19 Mar 2020
Please try the v1.21.15 prerelease and let us know if it resolves your performance issue.
I confirm that the performance issues are gone. 馃帀
jonaspm
on 19 Mar 2020
I confirm that the performance issues are gone. 馃帀
Same here.
juhoheikkilae
on 19 Mar 2020
Great that it is working. However, I am not sure how to install a pre-release extension. The .visix file is failing, even after uninstall of current .14 version and a restart.
Grandizer
on 19 Mar 2020
@groundsquirrel Thanks for the report. Closing this now that 1.21.15 has been published.
JoeRobich
on 20 Mar 2020
Related issues
mattwoberts
路
3Comments
rucka
路
4Comments
nguillermin
路
3Comments
IdeoG
路
3Comments
ZeldaZocker
路
3Comments
Most helpful comment
Latest version really does seem to tank vscode and break a number of other extensions like gitlens just isn't responsive at all, and vscode cpu% is chewing cores, it also breaks a few other extensions that relied on the old extension name. I've rolled back to the previous version.