vscode-stripe: libcoreclr.dylib leads to libsystem_c.dylib!abort and crashing repeatedly
Issue moved from dotnet/vscode-dotnet-runtime#252
- Please respond to @winzig.
From @winzig on Wednesday, June 30, 2021 4:53:47 PM
Initially reported to vscode an issue where chrome_crashpad_handler was constantly running with high CPU/disk usage here: https://github.com/microsoft/vscode/issues/127392 (and someone else reported it here: https://github.com/microsoft/vscode/issues/124713)
They looked at the attached dmp’s and stated:
Thanks for the logs, all of them point to crash in the dotnet runtime specifically a call from libcoreclr.dylib leads to libsystem_c.dylib!abort case. Since I don’t have symbols for this extension binary, I can’t specifically say why.
They suggested I open an issue here and attach my dmp files, so here it is.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 33 (12 by maintainers)
Commits related to this issue
- Do not restart if C# server exits. If the C# server fails to start up for an unrecoverable reason, restarting it will cause repeated crashes: https://github.com/stripe/vscode-stripe/issues/292 — committed to stripe/vscode-stripe by gracegoo-stripe 3 years ago
- Do not restart if C# server exits. (#293) If the C# server fails to start up for an unrecoverable reason, restarting it will cause repeated crashes: https://github.com/stripe/vscode-stripe/issues/... — committed to stripe/vscode-stripe by gracegoo-stripe 3 years ago
Thanks so much for all those logs! I have a way to reproduce this now, I’d recommend disabling the extension for .NET workspaces for now so it doesn’t impeded your productivity! I’ll let you know when we have a version out for you to test.
Thank you @winzig and @pascallapradebrite4 for reporting and helping debug this issue! I will keep this issue open to look into the root cause of the startup failure.
Just released 2.0.3 which addresses the constant restarting of the server. This version doesn’t address the missing MSBuild instance, but it will stop trying for you after the initial attempt. You will still be able to leverage most of the Stripe extension’s features that do not depend on the language server.
Thanks so much for the additional info, Pascal! Glad to hear that it’s not impacting your other projects, we don’t start up the C# language server unless we detect that you’re working on a .NET project.
5.0 is the runtime that we use to run Stripe’s C# language server app and 5.07 is installed by the vscode-dotnet-runtime extension we depend on because that’s the latest version – nothing to do with the runtime your project depends on
Thanks for reporting, taking a look.