Omnisharp freezes during extension initialization with excessive CPU usage

Environment data

VS Code version: 1.42.1 C# Extension version: 1.21.13

Steps to reproduce

• Startup VS Code
• Wait for intellisense to populate, which doesn’t happen.
• Try to restart Omnisharp via the command pallete; it doesn’t respond.

Look at the extension host log, which will list a sequence of:

[exthost] [error] [ms-dotnettools.csharp] provider FAILED
[exthost] [error] Problem invoking 'GetCodeActions' on OmniSharp server: Error: Pending request cancelled: /v2/getcodeactions

Expected behavior

For the extension to be well behaved.

Actual behavior

The extension is broken and doesn’t initialize correctly. Occasionally VSCode will complain about excessive CPU usage.

Once frozen have to close VS Code down (as the command pallete to restart Omnisharp doesn’t work) and start it back up, then let Omnisharp sit there spinning rims for ~5m before whatever is blocking it gives up and the extension hopefully initializes without hanging indefinitely again.

[kieranbenton]

@JoeRobich just upgraded again to .15 and it does indeed look as if this has been resolved. Cheers!

[JoeRobich]

@kieranbenton Can you give us more details about you project? Others have reported this same issue with asp.net projects containing large ‘node_modules’ folder or Unity projects with a large ‘PackageCache’ folder. What type of project are you building and do you have any folders with many nested subfolders in your project?