Get all your news in one place.
100’s of premium titles.
One app.
Start reading
Windows Central
Windows Central
Technology
Richard Devine

Microsoft is even gobbling up PC resources on Linux — Visual Studio Code could be hogging hard drive space

A screenshot of Visual Studio Code showing a toml file.

Microsoft's Visual Studio Code is one of the most popular coding apps around, with the added benefit of being cross-platform.

Unfortunately, on Ubuntu, there's a pretty nasty bug occurring with the official Snap package delivered via Canonical's store.

As highlighted by How To Geek, the bug regards deleted files not being properly sent to the system trash, and, over time, building up to potentially sizable chunks of storage space being eaten alive.

Per How To Geek:

"When you delete a file or folder in Visual Studio Code, the data is usually moved to your system's trash directory or recycle bin. That way, you can restore the file if needed, at least until you empty the trash. However, when Visual Studio Code is installed as a Snap package on a Linux computer, the file is moved to a trash folder within the Snap package, instead of the system trash bin."

VS Code has versions for basically every platform you could need. (Image credit: Windows Central)

This behavior conflicts with the system trash, in so much as when that's emptied, the VS Code trash is not. This can lead to it sitting, filling up over time.

The issue was first reported back in November 2024, with users becoming aware that potentially hundreds of gigabytes of their storage were being held hostage by the Snap package's trash that they'd been unaware of.

We're now in 2026 and the issue remains. The affected directory can be found by navigating to ~/snap/code/current/.local/share/Trash.

So, if you've been using the official Snap package version of VS Code on Ubuntu, what can you do? The easiest solution is to stop. Microsoft offers installers for all major versions of Linux, so for Ubuntu, you can grab the .deb one from the official download page.

There is also a .rpm version if you're on something like Fedora, and an unofficial Flatpak package, too.

In the grand scheme this bug is probably small fry, but the fact it's been left unattended for over a year isn't a good look for the VS Code team. Another day we're hearing about bugs in Microsoft software. It'd be nice to hear less of these.


Follow Windows Central on Google News to keep our latest news, insights, and features at the top of your feeds!


Sign up to read this article
Read news from 100’s of titles, curated specifically for you.
Already a member? Sign in here
Related Stories
Top stories on inkl right now
One subscription that gives you access to news from hundreds of sites
Already a member? Sign in here
Our Picks
Fourteen days free
Download the app
One app. One membership.
100+ trusted global sources.