-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VSCodium creates log files in ~/.config/VSCodium/logs/ which is not an appropriate place for log files. #1903
Comments
I agree
That's bad! On VSCode, does VSCode generate the same error ( By looking at VSCode, If A patch is needed! |
I had a college check (because I do not have VSCode). The VSCode seems to create log files under the same location. He had about 11 MBytes of accumulated log files in the config dir. |
I agree.
You could report the issue to VSCode. In the meantime, you could use the argument |
Submitted it here: microsoft/vscode#213322 |
I've provided my feedback... |
Describe the bug
VSCodium creates logs in the directory ~/.config/VSCodium/logs/
The ~/.config directory is not the right place to put log files.
In my installation, these logs look like this:
~/.config/VSCodium/logs/20240522T223215/window1/renderer.log
The content is:
2024-05-22 22:42:50.153 [error] [Extension Host] Errored result: [object Object]
2024-05-22 22:42:50.153 [error] [Extension Host] Errored result: [object Object]
2024-05-22 22:42:50.154 [error] [Extension Host] Errored result: [object Object]
2024-05-22 22:42:50.155 [error] [Extension Host] Errored result: [object Object]
The fact that these errors are created probably goes to PlatformIO or IntelliSense and after 1 hour of work, these files can make up hundreds of MBytes.
The bug that I'm reporting here is the mere fact that log files are generated in ~/.config. The log file path suggests it is created by the application core itself (window1 render task) and not by any plugin. The ~/.config directory is not appropriate for logs. Also, these never seem to be cleaned up and accumulate ad infinitum.
Please confirm that this problem is VSCodium-specific
Please confirm that the issue/resolution isn't already documented
To Reproduce
For me it's as simply as starting codium in a directory that needs platformio, but probably other ways work as well.
Expected behavior
Put log files somewhere else, I'd vote for the temporary system directory /tmp/ . You can use mkstemp() or similar to create a directory there.
Screenshots
N/A
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: