Cursor Bug: Cursor extension terminated unexpeted 3 times within the last 5 minutes

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

This bug specifically appears in certain folders (i.e. when opening a folder of a code base). And it doesn’t require interacting with any model, it’ll just show extension error. The error seems to be tied to Cursor_Socket which is probably cursor’s internal access.

Steps to Reproduce

After a while of struggling with it - it seems to appear in folders with:

  1. Lots of files
  2. LOTS of submodules with lots of files (yes lots of files)
  3. I didn’t pull the submodules, so these modules are still on our internal github server.

Expected Behavior

Shouldn’t have an extension error at all, this basically blocks it from interacting with the model

Operating System

Windows 10/11

Version Information

Version: 3.1.15 (system setup)
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

Happens with all models, doesn’t matter or it will still show up without using a model.

Does this stop you from using Cursor

Yes - Cursor is unusable

The way i worked around it is to turn this off - indexing repositories for instant grep. I think you should be able to repro it by creating a random github directory with lots of files (probably in orders of tens of thousands) and then create git submodules within it with again, tons of files. Something is probably overloading the cursor_socket extension.

Hey @Tony_Ku!

Thanks for the report. There are a few known bugs here, and I’d love to find out if one matches your case.

Would be great if you could run Ctrl + Shift + P > Developer: Open Logs Folder, move up one folder to find the session that crashed, zip it up and attach them here. I can also open up a private DM if you’d prefer!

I already found the workaround above - it has to do with accessing submodules with too many files with indexing and seems to overload the extension. Cannot send any files outside of our network, sorry.