vscode-csharp: 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.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 4
- Comments: 19 (9 by maintainers)
@JoeRobich just upgraded again to .15 and it does indeed look as if this has been resolved. Cheers!
@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?
@NTaylorMullen So it’s a symptom, then? Good to know.
I’ve reverted back to 1.21.12 in the meantime via VSIX install so it also has the old publisher ID, avoiding the issues related to the publisher ID switch as well.
Taken as a whole 1.21.13 is just broken. Imho it should be pulled and maybe 1.21.12 should just be republished under the new publisher ID with no further changes.