TechFixSignal
VS Code

VS Code Window Terminated Unexpectedly Crashed Code 135

When VS Code shows The window terminated unexpectedly reason crashed code 135, launch with ozone-platform x11, disable GPU, or move off 1.129.0.

Reviewed by TechFixSignal EditorialSee how this guide is verified

Last checked
Sep 14, 2026
Applies to
Windows, Mac, Desktop
Fix status
Community Confirmed
Fastest useful check

Quick answer

Match The window terminated unexpectedly (reason: 'crashed', code: '135'). On Wayland Linux, launch with code --ozone-platform=x11 so GPU stays on. If that is not enough, try code --disable-gpu. If you are on 1.129.0, fully quit every VS Code process, then pin or reinstall 1.128.1, or update to 1.129.1 or newer. Reload Window alone is not enough. This is not the Extension host terminated unexpectedly 3 times within the last 5 minutes toast.

On this page

What we're seeing

  • The exact dialog is The window terminated unexpectedly (reason: 'crashed', code: '135').
  • Independent July 2026 first-hand microsoft/vscode issues quote that dialog on Ubuntu Wayland with NVIDIA, Linux Mint, Intel, and AMD systems after 1.129.0.
  • First-hand leftovers include launching with --ozone-platform=x11, launching with --disable-gpu, and leaving 1.129.0 for 1.128.1 or 1.129.1+.
  • Related dumps in the same cluster mention SIGBUS around shared memory, which is why version pin or update is a try-today path.
  • The toast Extension host terminated unexpectedly 3 times within the last 5 minutes is a different fingerprint with different leftovers.

Start here

Try these first

Fix 1

Confirm the window crashed code 135 dialog

Community Confirmed

Match the window crash dialog before changing GPU flags or rolling back a build.

  1. Read the dialog. This guide is for The window terminated unexpectedly (reason: 'crashed', code: '135').
  2. If the message is Extension host terminated unexpectedly 3 times within the last 5 minutes, stop here and use that separate guide.
  3. Note Help → About version and whether you are on Wayland, X11, NVIDIA, Intel, or AMD.

Applies to Windows, Mac, Desktop

Fix 2

Launch with --ozone-platform=x11

Community Confirmed

July 2026 first-hand Wayland reports with the exact code 135 dialog cleared after launching VS Code under X11 while keeping GPU acceleration.

  1. Fully quit VS Code so no leftover process remains.
  2. From a terminal, launch with code --ozone-platform=x11.
  3. Open the same folder and confirm the window stays up.
  4. If you already run X11 only, this flag may do nothing. Move to the GPU or version leftover below.

Applies to Desktop

Fix 3

Launch with --disable-gpu

Community Confirmed

The same first-hand cluster also recovered with --disable-gpu when the ozone flag was not enough or the session was already on X11.

  1. Fully quit VS Code.
  2. Launch with code --disable-gpu.
  3. Confirm the dialog does not return, then decide whether to keep that launch flag in your desktop shortcut.

Applies to Windows, Mac, Desktop

Fix 4

Leave 1.129.0 for 1.128.1 or 1.129.1+

Community Confirmed

First-hand bisects in July 2026 show 1.128.x stable and 1.129.0 crashing with code 135, with later 1.129.1+ builds recovering for some reporters. Prefer backing up settings before a downgrade.

  1. Confirm Help → About shows 1.129.0, or that crashes started right after that update.
  2. Export or copy settings and keybindings if you will downgrade.
  3. Fully quit every VS Code process, then install 1.128.1, or update to 1.129.1 or newer.
  4. Relaunch and confirm The window terminated unexpectedly (reason: 'crashed', code: '135') is gone.

Applies to Windows, Mac, Desktop

Device notes

Windows
--disable-gpu and leaving 1.129.0 apply on Windows. The ozone X11 leftover is mainly for Linux Wayland.
Mac
Prefer --disable-gpu or a version change if this dialog appears on macOS. Ozone X11 is not a Mac path.
Desktop
Linux Wayland plus NVIDIA was the densest first-hand cluster for code 135. Try ozone X11 first, then disable-gpu, then leave 1.129.0.

Official information

Checked on 14 September 2026, microsoft/vscode GitHub issues that quote The window terminated unexpectedly (reason: 'crashed', code: '135') document first-hand leftovers for --ozone-platform=x11, --disable-gpu, and leaving 1.129.0 for 1.128.1 or later 1.129 builds. There is no separate VS Code Docs page that names only this exact dialog.

Sources

Keep troubleshooting

Related problems