Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Perf: OmniSharp takes several minutes to load projects

See original GitHub issue

OmniSharp is timing out on loading solutions with large files within the default timeout in VS code (60 seconds). The timeout can be increased, but the solution still takes several minutes to load. On some solutions, it takes 3-4 minutes to load the project system.

Repro: git clone https://github.com/aspnet/Blazor-Hackathon dotnet restore Blazor.Core.sln Open VS Code and try to load Blazor.Core.sln

Canonical link: https://github.com/aspnet/Blazor-Hackathon/tree/a8c341fcb5a519fb7c931eaa9ba23bde560433ef

Result The output log shows OmniSharp trying to load the project correctly, but it times out after 60 seconds with an error printed to the Output > Omnisharp Log window in in VS Code.

Workaround Increase project load timeout to 4 minutes

{
  "omnisharp.projectLoadTimeout": 240
}

Details VS Code: 1.14.2 C# Extension: 1.12.0-beta3 Mono: 5.2.0.196 OS: macOS 10.12.5 dotnet: 2.0.0-preview2-06497

Issue Analytics

State:
Created 6 years ago
Reactions:19
Comments:19 (8 by maintainers)

Top GitHub Comments

7reactions

vchirikovcommented, Oct 5, 2020

We have about 260 projects, and omnisharp is completely unusable, because of slow loading of projects. I know that msbuild is slow, and it can takeup to 30 sec to evaluate of all csproj properties (with 1 thread) but with omnisharp ProjectManager init took 15 min.

6reactions

davidfowlcommented, Feb 13, 2018

I’m hitting this too. Larger solutions need more time to load. Can VS code load projects in parallel?