OBS Studio Always Shows "Quit Unexpectedly" on Exit – Safe Mode Prompt on Reopen

GregTC

New Member
Hi everyone,

I’m encountering a persistent issue with OBS Studio on macOS 15.3 with OBS 31.0.1. Every time I close OBS—whether using Cmd + Q or through the menu—it gives the error message:

"OBS Studio quit unexpectedly."
Then, when I reopen it, I always get prompted to choose between opening OBS normally or in Safe Mode.

OBS itself runs fine while in use; this only happens when closing it.

Troubleshooting Steps I've Tried (No Success):​

✅ Updated macOS and OBS to the latest versions
✅ Disabled Browser Source Hardware Acceleration
✅ Reset OBS settings by renaming ~/Library/Application Support/obs-studio/
✅ Fully uninstalled & reinstalled OBS, including manually deleting all related files
✅ Checked macOS permissions (OBS has Full Disk Access)
✅ Tried running in Safe Mode (same behavior as normal mode)
✅ Checked logs in Terminal (OBS runs fine until exit)

The crash report suggests an issue related to Chromium Embedded Framework (CEF). Has anyone else encountered this on macOS 15.3? Any other ideas on how to fix it?

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process: OBS [1884]
Path: /Applications/OBS.app/Contents/MacOS/OBS
Identifier: com.obsproject.obs-studio
Version: 31.0.1 (12846547662)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2025-02-03 10:08:54.1731 +0000
OS Version: macOS 15.3 (24D60)
Report Version: 12
Bridge OS Version: 9.3 (22P3051)
Anonymous UUID: 19373D99-4FE6-8DD6-A158-895FC55167AF


Time Awake Since Boot: 980 seconds

System Integrity Protection: enabled

Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1884]

VM Region Info: 0 is not in any region. Bytes before following region: 4313931776
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 101216000-10164c000 [ 4312K] r-x/r-x SM=COW /Applications/OBS.app/Contents/MacOS/OBS

Kernel Triage:
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter

Thanks in advance!
 

saved_92

New Member
I've had the same problem for over a week. I've tried downloading a previous version and I get the same errors.
 

AaronD

Active Member
Put a logfile into our automated Analyzer. (link in my signature) See what it comes up with.

One common source of crashes is a bad plugin. One of the well-advertised ones is well-known on these forums to be poorly written.
 

rockbottom

Active Member
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1884]

I searched this & it may be caused by another app.
 

heavymcd

New Member
I'm getting this same issue on an M1 Max Mac Studio, macOS 15.3.1, and OBS 31.0.1.

I've literally done a full "transfer this computer" wipe of the system, the only thing I re-installed was OBS straight off the website, still get it. Zero plugins, zero profiles/scenes setup, and not a single other application installed on the entire computer that didn't come preinstalled from Apple.
 

EvanLN

New Member
It’s the same issue on my M2 MacBook, but only when the ‘YouTube live control panel’ dock is used. If not, no crash.
 

todahnyc

New Member
It’s the same issue on my M2 MacBook, but only when the ‘YouTube live control panel’ dock is used. If not, no crash.
This really seems to be the issue, I've disabled YouTube live control panel from Docks within OBS and this annoying message finally stopped.
 

GregTC

New Member
Just tested removing the YouTube dock and open closed a few times, and it seems not to cause the issue. It's good to get rid of the error, but it is also useful to have the YouTube dock.
 

Langjjj

New Member
Did all the uninstalls and restarts without solving the crash. Definitely the "YouTube Live Control Panel" – when disabled OBS shuts down normally. Thanks for sharing.
 
Top