Cursor element selector crashing Cursor

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In Cursor’s built-in browser, the “Select Element” tool allows you to select an element. But, instead of adding that element to the chat, it crashes the app. I have to restart it.

Steps to Reproduce

  1. Run a NextJS with yarn
  2. Try to select an element

Expected Behavior

Should not crash when inspecting element

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 2.6.21
VSCode Version: 1.105.1
Commit: fea2f546c979a0a4ad1deab23552a43568807590
Date: 2026-03-21T22:09:10.098Z
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: Darwin arm64 25.3.0

For AI issues: which model did you use?

Composer 2

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. I can see the screenshot with “The window is not responding” and that confirms the element selector is freezing the main process.

This is a known issue with the element selector in the built-in browser. The team is aware and the bug is logged.

One question, was the browser tab docked inside the main Cursor window, or did you pull it out into a separate window? If it was in a separate window, that’s a known trigger. Workaround: keep the browser tab inside the main window.

If it still crashes even with a docked tab, let me know, that helps us prioritize it.

Thanks for the speedy reply.

its a docked tab.

image

Hi. Colleague is also having a similar issue. Please let us know if we can provide anything to help resolve bugs.

Specifically, when colleague opens Cursor browser in tab (not external tab) and colleague selects element, Cursor crashes.

Hey, thanks for confirming. This is a known issue with the element selector, the team is aware, and your report helps us prioritize it.

Could you check which Cursor version your colleague is on, and what OS they’re using? That’ll help with debugging.

@Jack_McGregor thanks for confirming the tab is docked. That means it’s not only an undocked issue. We’ll factor that in too.

Let me know if anything else comes up.

Hey again

so this seemed to have been fixed but it started again yesterday, was there an update? I can’t use the element inspector at all, it crashes Cursor

Hey Jack. It’s a bummer this came up again. The issue for this bug is still open, and there’s no fix timeline yet.

To confirm this is a regression, could you please share:

  1. Your current Cursor version Cursor Settings > About, or Cursor > About Cursor.
  2. The same setup as in March, docked tab, NextJS, or did anything change?
  3. If it happens again, a screenshot or a quick description of when it crashes right after clicking an item, on hover, etc.

With that info, I’ll update the internal report as a regression.

Sure

Version: 3.1.17
VSCode Version: 1.105.1
Commit: fce1e9ab7844f9ea35793da01e634aa7e50bce90
Date: 2026-04-19T19:33:58.189Z
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: Darwin arm64 25.3.0

Same setup, but as per our other conversation Cursor on macOS consuming massive memory (40GB+) → “Your system has run out of application memory” - #14 by deanrie I’ve uninstalled a ton of extensions and on first glance it’s working again, but if it crashes again I’ll let you know. You have my previous list of extensions and the new list on that thread, maybe the ones I removed will give you an idea

Thanks for the update.

One interesting thing: removing extensions might not have been random. The element picker runs via IPC in the browser view, and an extension that hooks into the same events or the DOM could, in theory, trigger a crash. If you remember which ones you removed from that memory thread list, especially anything related to the browser, DOM, dev tools, screenshots, or webview, send them over and we’ll try to match it up.

If the crash comes back, let me know right away, ideally with a screenshot of the moment it crashes, like on click, on hover, or after selection.