search

microsoft / vscode-cpptools

Official repository for the Microsoft C/C++ extension for VS Code.
Other
5.51k stars 1.55k forks source link

Limit size of .browse.VC.db to avoid filling up disk #3470

Open letmaik opened 5 years ago

letmaik commented 5 years ago

I had situations where .browse.VC.db files where ~10GB (yes, lot's of source files to be indexed). I'm fine with this, but there should be some check in place that prevents those files from occupying all available disk space. How about going into some degraded-service behavior if less than 0.5GB (or similar) is available?

sean-mcmanus commented 5 years ago

Degraded service isn't really an option, but one potential workaround is to add folders to your files.exclude setting (be sure your regex evaluates to folders and not files, unless you change the C_Cpp.exclusionPolicy to "checkFilesAndFolders".

lukka commented 4 years ago

The ms-vscode.cpptools is occuping around 40Gb on my hd, that is out of disk space now. It would be nice to if the extension would offer a section to manage the internal storage for each workspace, i.e. where i can see and delete the related files.

image

letmaik commented 3 years ago

Just ran into the same issue again. I used VS Code remote and the extension filled up the disk completely, which I didn't notice. After a restart I couldn't ssh in and had to do an elaborate recovery on Azure (of course, freeing up disk space via Azure's serial console would theoretically work, but only if you had setup a user/password admin user in advance, because of course the "reset password" function to create such a user only works if Azure's vm agent is running, and it crashed during boot because there was no disk space).

major-mayer commented 1 year ago

Same problem here, my workspaceFolder has grown to over 10 GB and is slowly filling up my SSD. It would be nice if there would be some way to delete those files without manipulating the file system itself and thereby breaking other extensions by accident. I think that those files would need to be re-generated when the workspace is opened again, but at least the space is freed until you open the workspace again.

djr-spectrummfg commented 4 months ago

Mine was 39GB which is completely unacceptable.