You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this issue occur when all extensions are disabled?: Yes
VS Code Version: 1.85.2, applies to any current version AFIK
OS Version: Linux
Description: By default, VSCode creates log files at the location ~/.config/Code/logs/, e.g. /home/username/.config/Code/logs/20240522T223215/window1/renderer.log This is not a proper location for log files and they never get cleaned up. The .config directory is for configuration and meant to be backed up by the user. It is not meant to be filled with logs by the application.
I've noticed the issue because platformio generated hundrets of MBytes of logs in merely a few hours, all of them looking like "2024-05-22 22:42:50.155 [error] [Extension Host] Errored result: [object Object]". These occuring in that frequency and being completely useless at the same time is a different topic. However, a misbehavior can easily fill hard drives in completely unexpected locations.
Steps to Reproduce: Check your config dir see how many MBytes of logs you have in there.
Solution: The log directory should, by default, be placed somewhere else, e.g. in /tmp/.code-username/ or using mkstemp(). Observe practices how to create temporary files to avoid issues. For instance "/tmp/.code-username" might already exist and/or be a file or symlink to something else.
The text was updated successfully, but these errors were encountered:
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.89.1. Please try upgrading to the latest version and checking whether this issue remains.
Does this issue occur when all extensions are disabled?: Yes
Description: By default, VSCode creates log files at the location ~/.config/Code/logs/, e.g. /home/username/.config/Code/logs/20240522T223215/window1/renderer.log This is not a proper location for log files and they never get cleaned up. The .config directory is for configuration and meant to be backed up by the user. It is not meant to be filled with logs by the application.
I've noticed the issue because platformio generated hundrets of MBytes of logs in merely a few hours, all of them looking like "2024-05-22 22:42:50.155 [error] [Extension Host] Errored result: [object Object]". These occuring in that frequency and being completely useless at the same time is a different topic. However, a misbehavior can easily fill hard drives in completely unexpected locations.
Steps to Reproduce: Check your config dir see how many MBytes of logs you have in there.
Solution: The log directory should, by default, be placed somewhere else, e.g. in /tmp/.code-username/ or using mkstemp(). Observe practices how to create temporary files to avoid issues. For instance "/tmp/.code-username" might already exist and/or be a file or symlink to something else.
The text was updated successfully, but these errors were encountered: