vscode: File operations get slow to a point of being unusable
#154085 is closed, but the bug is not fixed.
Version: 1.70.2 Commit: https://github.com/microsoft/vscode/commit/e4503b30fc78200f846c62cf8091b76ff5547662 Date: 2022-08-16T05:36:25.715Z Electron: 18.3.5 Chromium: 100.0.4896.160 Node.js: 16.13.2 V8: 10.0.139.17-electron.0 OS: Linux x64 5.15.0-46-generic
This bug has rendered VSCode nearly impossible to use. After some time, all active instances of the application will cease reading/writing files and the only way to restore function is to kill the application in such a way that no backups are provided anyway. Is there any way to completely disable this backups feature? It is presently counter-productive.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 32 (14 by maintainers)
@rico345100 if you have a repro of your problem please use the instructions at https://github.com/microsoft/vscode/wiki/Performance-Issues to open a new issue with repro steps.
Ok, I suggest both of you to collect and send me logs (mail is fine) from a session where things get slow. You can run a command in VSCode “Open Logs Folder” and zip it and send it to me.
No, no gradual slowdown, at least not that I’ve noticed. Things go abruptly from normal operation to total lockup. The “discarding backups” dialog does, however, occur after the onset of problems. The file explorer tab will show the blue bar animation as though it is loading something, and files will not open or save. This condition lasts indefinitely. Closing all sessions of the application is necessary to restore function, and it is upon doing so that the “backups” dialog is encountered.