vscode: When I use vscode to open a folder, many empty file with invalid code automatically are generated.
Does this issue occur when all extensions are disabled?: Yes/No
- VS Code Version:
- OS Version: Sorry for I had deleted the VS Code, because I worry if the computer is attacked by virus. But VS Code is recent version. I update VS Code yesterday. Steps to Reproduce: When I use vscode to open a folder, many empty file with invalid code automatically are generated. And I use OpenFOAM(a software) to wmake(make) some function, the contents in some “.H” and “.C” which are related with this function is disappeared, these files become empty, though these files “.H” and “.C” are still exist.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 9
- Comments: 60 (20 by maintainers)
Hello Due this bug the content of one of my source file which had 3000 line, was deleted . I don’t use version control system. How can i restore it?
Man, I can’t wait to read the blog post explaining what happened here
Additional information. The deletion of contents of files was not restricted to my working folder!
It has even managed to delete contents outside this folder, for example my ‘windows kits’ has been destroyed and I don’t know to what extend, but the following file, for example, is completely empty now:
I do not know if the issue is only affecting parsing of ‘include’ files or that it could possibly have touched completely unrelated files as well.
A few more files were affected:
Searched on size 0, modified today
Same issue here. Some empty files with random filenames are created when I open the folder using Remote SSH.
Some susceptible filenames seem like SQL.
Version: 1.65.2 (user setup) Commit: c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1 Date: 2022-03-10T14:33:55.248Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.19044
Remote OS is CentOS 7
c/c++ extension v1.9.4 's problem.
https://github.com/microsoft/vscode-cpptools/issues/9046
node-ipc?
For reference: https://github.com/microsoft/vscode-cpptools/issues/9041#issuecomment-1071991779
I was not trying to imply that this specific bug could have slipped through. Was trying to imply that nobody is ever perfect and mistakes can happen. Even on a thoroughly tested release. “Looking at you, any random game development studio” 😃
@mhavill We’ve finally found the repro and a fix for the root issue for our pending 1.9.6 release. We’re very sorry for any problems this may have caused and our looking into various things that could potentially prevent this from happening again.