-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
VSCode holds *.asar file locked though I've even did not open it in editor, which leads to "The process cannot access the file because it is being used by another process." #80146
Comments
Duplicate of #62518 (comment) , but that one was not fixed |
@ivictbor in that screenshot, what is the full command line of the Code process that locks the asar file? Trying to understand which of our processes this is. |
@bpasero thanks for reply, here how it looks, though it has no |
@dbaeumer looking at it this seems to be a language server. Didn't you recently push a change there to disable asar support? |
This got fixed in the LSP libraries lately. I think it got introduced when @alexandrudima added asar support to the extension host and removed the env when starting it. Commit is microsoft/vscode-languageserver-node@1e7962e |
@dbaeumer Is there a new version I can adopt? |
No, will come out this week. |
Steps to Reproduce:
npm run build
win-unpacked\resources\app.asar: The process cannot access the file because it is being used by another process.
Does this issue occur when all extensions are disabled?: Yes/No
Yes, tried
code --disable-extensions
, Open Folder.The text was updated successfully, but these errors were encountered: