I’m just going to put this picture here:
Jesus fucking christ
1 Like
Hi,
What version of SonarQube for VSCode are you using?
Thx,
Ann
Hello @atomey, thanks a lot for the report!
Just to clarify, as @ganncamp highlighted, we’d still like to know the version, but this behavior is not expected regardless of which version you use.
Please note that part of the fix (deleting issue storage folders & files older than 3 days) will be part of the upcoming release (coming next week). In the meantime, you can safely remove all folders starting with xodus-..., as well as .sonarlinttmp_... under the .sonarlint directory.
In the longer term, we are considering more sustainable solutions to possibly stop relying on the temporary folders altogether. This has not been specified yet. It is just to say that we are aware of the problem and actively trying to solve it.
Finally, since your case seems extreme, could you please provide further details on which language you are coding in and whether you are using Connected Mode?
We really appreciate your patience and the time you took to report this instead of simply uninstalling SonarLint and leaving it there. 
All the best,
Sophio
2 Likes
OP is not alone on this one. I routinely see about .5G per day thrown into the folder.
I’m on Windows 10.
I routinely switch between two different typescript / react projects. Both are rather large.
One of the projects is a sub-folder in a larger .NET project, but I only open the sub-folder in VSCode.
Neither project is connected.
Right now I’m managing it with a clean-up task that runs on startup.
1 Like
Thanks for sharing the details @melgish
We are looking into this.