To solve the problem of slow expansion of VSCode on Linux, please follow the following steps: 1. Check the system resources to ensure that there is enough memory and CPU available, use top or htop to monitor and close unnecessary processes; 2. Disable unused extensions, especially automatic formatting, code checking and other high resource occupancy tools, try to start VSCode in no-extension mode; 3. Troubleshoot the extension itself, view logs and community feedback, and consider updating or replacing lightweight alternatives; 4. Optimize VSCode configuration, upgrade to the latest version, avoid using Snap installation, clean cache, or try the Insider version. By gradually adjusting these aspects, performance can often be significantly improved.

If you're using VSCode on Linux and extensions are running slowly, you're not alone. This is a common issue that many users face, especially when working with resource-heavy or poorly optimized extensions. Let's break down what might be causing the slowdown and how to fix it.

1. Check Your System Resources

One of the most common reasons for slow extensions is simply not having enough system resources available.

• RAM usage – If your system is low on memory, VSCode (and its extensions) will run slowly. Extensions often run in separate processes, so each one can consume additional memory.
• CPU usage – Extensions like linters, formatters, or language servers can spike CPU usage, especially if they're analyzing large files or projects.
• Disk I/O – Slow disk performance (especially with HDDs or certain SSD settings) can also cause delays when loading or saving files.

What to do:

• Use top or htop to monitor resource usage while working in VSCode.
• Close unecessary applications or background processes.
• Consider upgrading hardware if you're consistently maxing out resources.

2. Too Many Extensions Enabled

Even on fast machines, having too many extensions enabled at once can add up. Some extensions start background processes or hook into file events, which can create overhead.

Common culprits include:

• Auto-formatters (eg, Prettier, Black)
• Linters (eg, ESLint, Flake8)
• Language servers (eg, Python, JavaScript/TypeScript)

Tips:

• Disable any extensions you don't actively use.
• Use the command palette ( Ctrl Shift P ) and search for "Manage Extensions" to disable or uninstall them easily.
• Try launching VSCode with all extensions disabled ( code --disable-extensions ) to see if performance improves.

3. Extension-Specific Issues

Some extensions just aren't optimized well for Linux. You may be running into bugs or compatibility issues specific to your setup.

How to diagnose:

• Open the Extensions view ( Ctrl Shift X ), and look at the output logs for individual extensions.
• Check the extension's GitHub page or the VSCode Marketplace reviews for known issues on Linux.
• Try updating or reinstalling the extension.

A few things to try:

• Switch from a built-in extension version to a globally installed one (eg, using a global ESLint install instead of the bundled version).
• Replace heavy extensions with lighter alternatives where possible (eg, using simpler themes or minimal syntax highlighters).

4. VSCode Itself Might Be Misconfigured

Sometimes the problem isn't with the extensions themselves but how VSCode is set up.

Things to check:

• Make sure you're using the latest stable version of VSCode.
• If you're using a snap package on Linux, consider switching to a .deb or .tar.gz version — snaps can sometimes have slower disk access due to sandboxing.
• Clear the VSCode cache: delete the contents of ~/.cache/Code (or similar, depending on your distro).
• Try using the insides build if you suspect a bug has been fixed in a newer version.

Performance issues with VSCode extensions on Linux usually come down to a mix of system limitations, extension bloat, or configuration quirks. Tweak these areas step by step, and you'll likely find a noticeable improvement.

Basically that's it.

The above is the detailed content of Why are my VSCode extensions so slow on Linux. For more information, please follow other related articles on the PHP Chinese website!