When using Shift Tab to indent code blocks, IDEA crashes

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I use the shift tab to indent code blocks, the IDE crashes. I have tried 3 times and it crashes every time. When the current number of lines is reduced to 48, there will be a crash phenomenon. When the number of lines in the code block is small, IDEA is normal.

Steps to Reproduce

Select more than 40 lines of code, use shift+tab indentation, IDEA crashes

Operating System

Windows 10/11

Version Information

Version: 3.14.7 (system setup)
VS Code Extension API: 1.128.0
Commit: a758f2241ca99fecf380180b6cbdbbce0f1f42c0
Date: 2026-07-30T06:41:34.009Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Yes - Cursor is unusable

In the last few seconds of the video, IDEA froze and crashed

Hey, thanks for the detailed report and the video.

We haven’t been able to reproduce it on our side yet. Outdenting with Shift+Tab on selections of 120+ lines on the latest build works without a crash. So it looks like something specific to your environment or that file. To dig deeper, could you help with a couple things:

  • The exact crash dialog text, especially the reason: and code: from the message “The window terminated unexpectedly”.
  • Logs from %APPDATA%\Cursor\logs\ (main.log and the renderer log around the time of the crash).
  • Does it still crash:
    • in a new plain-text file (not .vue),
    • when you run cursor --disable-extensions from the command line?
  • You’re on 3.14.7, please update to the latest stable (3.15.6) and check if it still happens.
  • If it still crashes, add "disable-hardware-acceleration": true to argv.json and restart Cursor. This helps rule out a GPU or driver renderer crash on Windows.

Items 3 and 5 will help us figure out if it’s an extension, GPU, or something else. Let me know what you find.

main.log (480 字节)

renderer.log (8.6 KB)

Hey, thanks for the logs and for updating to 3.15.6.

One catch: the renderer.log you sent is just a normal session start log entries from 15:13:33 to 15:13:54. The crash itself didn’t get captured there. There’s no crash stack, so we can’t see the cause from that file.

To capture the right log, please do this:

  1. Reproduce the crash Shift+Tab on 40+ lines in the same .vue, then let Cursor crash.
  2. Right after that, open %APPDATA%\Cursor\logs\ and grab the renderer log from the same session window where the crash happened. That one should include the stack and the reason. Also, please copy the exact crash dialog text, especially reason: and code: from “The window terminated unexpectedly”.

Also, can you confirm these points? This will narrow it down extension vs GPU vs something in the file:

  • On 3.15.6, does the crash still happen?
  • Does it crash in a new plain text file not .vue?
  • Does it crash if you launch cursor --disable-extensions from the command line?
  • If yes, add "disable-hardware-acceleration": true to argv.json, restart Cursor, and test again.

On our latest build, outdenting 120+ lines doesn’t crash, so it looks like something in your environment or this specific file. Your answers above will help us figure out where to dig next. Waiting for your results.