Linux users who installed Microsoft's Visual Studio Code as a Snap package may want to check to see whether files they sent to the trash with the app have actually been deleted.

A handful of Linux-based developers have found large amounts of supposedly deleted data on their computers, in some cases consuming hundreds of gigabytes of storage.

The reason for this is Snap – a Linux application packaging format – creates a local Trash folder for each VS Code version, one that's separate from the system-managed Trash, according to a VS Code [1]bug report dating back to November 11, 2024.

[2]

Not only that, but Snap keeps older versions of VS Code after updates, potentially [3]multiplying the number of local Trash folders and the trashed-but-not-deleted files therein. Emptying the system Trash folder doesn't affect the local instances.

[4]

[5]

Neither VS Code nor Snap offers a way to manage these local trash folders, though this can be [6]achieved with the command line .

The [7]root cause of the mess, [8]according to a Microsoft engineer , is an unfixed VSCode change from October 11, 2024, that [9]sets the [10]XDG_DATA_HOME environment variable equal to $SNAP_USER_DATA/.local/share .

[11]

"This creates a bogus Trash that's not the system one, and as such is unmanageable (and is carried over from update to update, gradually inflating)," the bug report explains.

[12]AI agents can't yet pull off fully autonomous cyberattacks - but they are already very helpful to crims

[13]DIY AI bot farm OpenClaw is a security 'dumpster fire'

[14]GitHub ponders kill switch for pull requests to stop AI slop

[15]Firefox makes AI optional, like it probably should have been all along

The bug may also cause issues beyond unexpected file retention, including messing up [16]fish terminal history, [17]interfering with uv Python installations , and [18]Jupyter Notebook problems , among others.

Robotics engineer Iván López Broceño reports finding [19]almost 200 GB of files that he believed he deleted.

Web developer Chris Hayes [20]said in the discussion thread that he found 44 GB of files in Snap's local Trash folder dating back two years.

Asked whether it's unusual for a bug like this to linger unfixed for more than a year, Hayes via email replied, "I'd say this is unusual when the risk is that the user can totally run out of space on their machine. In fact, that's how I first discovered it. I was running out of space, I pulled open Ubuntu's 'Disk Usage' and was pretty confused by how much space the VS Code snap was using."

[21]

Hayes, however, said he could understand how a bug like this might get lost in a massive repo like VS Code, which has [22]12,000+ open issues .

He added that the number of Linux VSCode users using Snap is probably not all that small. Snap, he said, the default for the Ubuntu App Store, though the default for VS Code is .deb for Linux users rather than Snap.

"I feel like a lot of people don't know about this because either they haven't run out of space or they didn't dig into their disk space usage," he said.

"The only other thing I'd add is running out of space on Linux can do some weird stuff, since Linux is so dependent on files for running everything. So, while this isn't a security vulnerability, it feels like it's getting lost in the sauce for something that can very much break your Linux machine. Not too long ago I was booting into a USB Linux to restore a corrupted file system on my desktop, it was probably for unrelated reasons, but it can definitely be a problem." ®

Get our [23]Tech Resources



[1] https://github.com/microsoft/vscode/issues/233649

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aYLScAQAU4P7GIN-xSAfIwAAAUI&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://github.com/microsoft/vscode/issues/237147

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aYLScAQAU4P7GIN-xSAfIwAAAUI&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aYLScAQAU4P7GIN-xSAfIwAAAUI&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://github.com/microsoft/vscode/issues/233649#issuecomment-3417893976

[7] https://github.com/microsoft/vscode/issues/237608

[8] https://github.com/microsoft/vscode/issues/237147#issuecomment-2684857364

[9] https://github.com/microsoft/vscode/commit/2d28c0a79c87c70be93dbe73fe0a18fa12e0e7e9

[10] https://specifications.freedesktop.org/basedir/latest/

[11] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aYLScAQAU4P7GIN-xSAfIwAAAUI&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[12] https://www.theregister.com/2026/02/03/autonomous_cyberattacks_not_real_yet/

[13] https://www.theregister.com/2026/02/03/openclaw_security_problems/

[14] https://www.theregister.com/2026/02/03/github_kill_switch_pull_requests_ai/

[15] https://www.theregister.com/2026/02/03/firefox_ai_kill_switch/

[16] https://fishshell.com/

[17] https://github.com/microsoft/vscode/issues/237608#issuecomment-2592580693

[18] https://github.com/microsoft/vscode/issues/237608#issuecomment-2609432967

[19] https://github.com/microsoft/vscode/issues/233649#issuecomment-3830929735

[20] https://github.com/microsoft/vscode/issues/233649#issuecomment-3152066259

[21] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/devops&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aYLScAQAU4P7GIN-xSAfIwAAAUI&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[22] https://github.com/microsoft/vscode/issues

[23] https://whitepapers.theregister.com/