...
| Code Block | ||||
|---|---|---|---|---|
| ||||
#To see your current quota: quota -s USERNAME #To see your 10 biggest files: top10 #To see the size of a specific directory such as .cache du -sh example_directory du -sh .cache #Misconfigured VS code logs set to never delete anything is a common cause of quota issues #To clear your cache clearcache |
Solution 5 (Long Term Mitigation)
VS Code Logs, general cache, and intellisense (a.k.a. cpp tools) cache all can grow exponentially depending on your settings. RAM and CPU usage can also grow exponentially. Setting hard limits in settings is generally a good idea. One user reported that with no limits set, their caches grew at 45 GB per hour until it completely filled their hard drive and crashed their computer.
MacOS: File > Preferences (Code > Preferences or Code > Settings on macOS) > Settings.
PC: in VSCode --> Ctrl + SHIFT + P --> type: settings --> click: "Preferences: Open Settings (JSON)"
If you do not want to use the IntelliSense caching feature (such as to work around a bug that may only occur when the cache is enabled), you can disable the feature by setting the IntelliSense Cache Size setting to 0 (or "C_Cpp. intelliSenseCacheSize": 0" in the JSON settings editor.
You can increase/decrease the available RAM for VS Code on its Settings.value you want to look for is maxMemoryForLargeFilesMB and change the value for your desired maximum RAM
Logging can be set to none, directed to
>/dev/null 2>&1 or a test file or set to a preset maximum sizeExternal Sources of information
https://code.visualstudio.com/docs/getstarted/settings
https://github.com/microsoft/vscode/wiki
...