-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting client failed: Error: spawn EBUSY
#732
Comments
Error: spawn EBUSY
@TylerHaigh I suspect this may be caused by the installation logic. I know you said that it resolves after restart (presumably once LS is already installed). With that in mind - can you try to reproduce this by:
I will try to reproduce this myself in a Windows VM. |
@radeksimko Followed instructions as follows:
After initial LS fails to start
|
I had the same issue. |
We believe we have resolved the issue with permissions to write files on installation in the linked PR and issue. Since this has been open for a long time, I'm going to lock and close this issue now. This is not an indication we are ignoring the issue, but rather an attempt to gauge if there are any new occurrences and to gain new diagnostic information. Please do open a new issue if problems persist for you. |
Originally posted by @TylerHaigh in #504 (comment)
After a VSCode restart, it seems to start fine
The text was updated successfully, but these errors were encountered: