Cursor Browser: Ctrl/Cmd+P (print) crashes the entire app

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I focus a page in the Cursor Browser and trigger print with Ctrl+P (Cmd+P on macOS), Cursor crashes immediately — the whole application closes. This happens when printing from the in-IDE browser (e.g. previewing a local site / PDF export via the system print dialog).

Related: Window.print() crashes cursor (window.print() from DevTools). My case is the keyboard print shortcut in the Browser, not a Canvas/console workaround.

Steps to Reproduce

  1. Open Cursor and start a local static/dev server (or open any page in Cursor Browser).
  2. Open the page in Cursor Browser (Simple Browser / agent browser).
  3. Focus the browser content.
  4. Press Ctrl+P (or Cmd+P on macOS) to open print.
  5. Cursor crashes / quits immediately.

Expected Behavior

The native print dialog should open for the Browser page, and Cursor should stay running.

Operating System

MacOS

Version Information

Cursor: 3.14.27
Commit: 047548b00c1a079373d74d00183f32510a4a41e0
OS: macOS 26.5.2 (25F84), Darwin arm64

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A

Additional Information

Suspected related upstream: electron/electron#50827 (window.print / native print dialog crash on macOS).
Staff note on the related thread: expected to be fixed when Cursor bumps Electron.
Workaround: open the same URL in Chrome/Safari and print there.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, thanks for the detailed report with steps and versions.

This is a known upstream Electron crash on macOS 26 Tahoe, the same electron/electron#50827 issue you found: Calling window.print() causes crash · Issue #50827 · electron/electron · GitHub. Printing via Cmd+P, window.print(), or the system print dialog goes through the native macOS print stack, and it crashes on this OS version. Cursor doesn’t add any custom print logic, so the trigger is the same whether you print from the Browser, the PDF viewer, or DevTools. There’s already a thread about it here: Window.print() crashes cursor.

For now, the best workaround is what you already found: open the same page in Chrome or Safari and print or export to PDF from there.

This should be fixed in a future Electron update. I can’t share an exact ETA yet, but I’ll post an update in the thread when there’s news.