Describe the Bug
Hi team,
I’m experiencing repeated kernel panics when using Cursor on my Mac mini M2 Pro (2023, 32GB RAM), running macOS Sequoia 15.5.
This issue only occurs on the Mac mini M2 Pro. I have a MacBook Pro M1 Pro with the same OS and workflow where the problem does not occur.
Steps to Reproduce
• Open Cursor
• Run a large “find in files” search, or use Cursor to generate code (especially when it triggers heavy background search with ripgrep)
• Within minutes, the system crashes and reboots (kernel panic)
Expected Behavior
no panic on kernel and no restarting.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.1.6 (Universal)
VSCode Version: 1.96.2
Commit: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850
Date: 2025-06-25T02:16:57.571Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
Additional Information
Key points:
• No user scripts or third-party daemons running. System is otherwise clean.
• Panic logs almost always reference either rg (ripgrep) or Cursor Helper (GPU).
• Disabling/uninstalling Cursor immediately stops the kernel panics.
• All hardware tests (RAM/SSD) pass, and S.M.A.R.T. is healthy.
panic(cpu 9 caller…): Releasing non-exclusive RW lock without a reader refcount! @lock_rw.c:2260
Panicked task … pid 14511: rg
Does this stop you from using Cursor
Yes - Cursor is unusable