How to Disable Hardware Acceleration in Visual Studio Code

If you need to test drive WordPress, Try it now!

Sharing is caring!

For some reason you may need to disable Visual Studio Code’s hardware acceleration. For example in Ubuntu it’s slow.

!Backup! Before you do anything backup the settings.

cp $HOME/.vscode/argv.json $HOME/.vscode/argv.json.backup

CTRL+SHIFT+P and type runtime you should see this kind of option.

Image

https://code.visualstudio.com/updates/v1_40

… or you can edit $HOME/.vscode/argv.json file. (Linux) that line is commented.

When I uncommented it Visual Studio Code started crashing without an error right after showing the loaded project.

After you make the changes restart Visual Studio Code.

Additional Tips

Check for Updates: Ensure that you are using the latest version of Visual Studio Code. Sometimes, updates contain performance improvements and bug fixes that could resolve issues without disabling hardware acceleration.
Graphics Drivers: Make sure your graphics drivers are up-to-date. Outdated drivers can cause performance issues with hardware acceleration.

Conclusion

Disabling hardware acceleration in Visual Studio Code can help improve performance on systems where it causes issues. By following the steps outlined above, you can easily disable this feature through settings, the command palette, or directly editing the argv.json file. Always remember to back up your configuration files before making changes to avoid potential problems.

Related

https://stackoverflow.com/questions/77249826/what-arguments-are-supported-in-vs-codes-argv-json-file

Sharing is caring!

If you need to test drive WordPress, Try it now!
This code shared in this post/site is provided "AS IS" without any warranties or guarantees of any kind. The authors and distributors of this code cannot be held responsible for any damage, data loss, or other issues that may arise from its use. It is strongly recommended that you test this code in a staging environment before deploying it to a live site. Always ensure you have proper backups and understand the implications of running this code on your WordPress installation. Use at your own risk.

Leave a Comment

Your email address will not be published. Required fields are marked *