Users of Microsoft’s Visual Studio Code on Linux, particularly those using the Snap package, have been experiencing significant disk space issues due to a persistent bug. This problem, first identified in November 2024, causes deleted files to accumulate in hidden trash folders. These are not cleared automatically and can persist over several updates, leading to substantial storage consumption.
The bug results in old versions of the software leaving residual data, effectively clogging up disk space with potentially hundreds of gigabytes over time. The root of the issue appears to stem from a change made in October 2024, where the XDG_DATA_HOME environment variable is incorrectly set, resulting in separate, unmanaged local trash folders for each version of VS Code.
Moreover, this problem isn’t just limited to disk space. Users have reported it causing additional challenges with their terminal history (specifically with the fish shell), as well as disruptions in Python installations and Jupyter Notebook functionalities. Despite awareness of the bug, there hasn’t yet been an integrated fix from either VS Code or Snap.
Though cumbersome, users can circumvent these issues by switching from the Snap version to either the DEB, RPM, or Flatpak versions of VS Code, which do not exhibit the same bug. Alternatively, users can manually clear the hidden trash using command line workarounds until an official solution is provided.

Collections

VS Code's Snap package on Linux has a bug causing deleted files to accumulate in hidden trash folders, consuming hundreds of gigabytes over time. The issue stems from an October 2024 change that incorrectly sets the XDG_DATA_HOME environment variable, creating unmanaged trash folders for each version. It also affects terminal history, Python installations, and Jupyter Notebook. Users can switch to DEB, RPM, or Flatpak versions, or manually clear trash folders as workarounds until an official fix is released.

Persistent Storage Issues with VS Code's Snap Version on Linux