SonarLint extension for VSCode is creating way too many tmp folders

I have the SonarLint extension for VS Code configured.

I executed npx npkill to clean up my computer a little with node_modules folders that I don’t use/need anymore, and found all these .sonartmp_xxx folders under C:\Users\<username>\.sonarlint folder, containing exactly the same package (eslint-bridge-bundle) over and over again.

There were more than 75 temp folders in total, with around 75 MB on each, that’s a total of more than 5.5 GB.

I must say that my co-workers don’t have this issue, therefore I am not sure if it is SonarLint’s fault.

I don’t know if there should be any logs that could help for this issue. If so, please let me know, and I will provide them.

Sin título

Thanks,

Hello, welcome to the community! And thank you for reporting this.

I noticed a similar behavior on my machine, which went unnoticed due to the use of the ~/.sonarlint folder, which is hidden on Linux. It looks like a regression in the deletion of temporary folders was introduced in a recent version.

Could you please tell us when the oldest one was created on your box? This could help us pinpoint the version in which the regression was introduced.