-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MacOS 15.3 Persistent Crash using OBS v31.0.1 #11801
Comments
This is a known issue, and a fix is being worked on. It has to do with the scene collection ending up in a "corrupt" state if you have an unclean shutdown after removing a Video Capture Device source. You should be able to resolve this in the meantime by loading the backup scene collection. You can do this by going into the If that does not resolve the issue, you should also be able to temporarily revoke the Camera permission from OBS, which will prevent the race condition from occurring on startup. |
Unfortunately the recommended fixes don't resolve the issue for me. I still can't so much as open OBS, even when uninstalling/reinstalling and rebooting. Hoping that #11884 will provide a solution, when merged. Update: I was able to resolve the issue by uninstalled OBS and deleting |
Perhaps interestingly (perhaps not), OBS retains a key in |
Operating System Info
macOS 15
Other OS
No response
OBS Studio Version
31.0.1
OBS Studio Version (Other)
No response
OBS Studio Log URL
Cannot get into OBS --- I pasted full crash report into section below.
OBS Studio Crash Log URL
No response
Expected Behavior
When I try to open OBS, it should open, not crash.
Current Behavior
When I go to open OBS, it crashes before the program appears on the screen. I get a crash report, and an option to try to reopen. I'm given the option to open normally or in safe mode – both result in seemingly the same crash. I do not have any plugins or unusual aspects of my setup that I'm aware of.
Steps to Reproduce
Note: I haven't yet restarted the computer; I decided to report this bug first in case I cannot reproduce it.
Anything else we should know?
The crash report was too long for this field, so I saved it as a plain text file.
OBS_CrashReport.txt
The text was updated successfully, but these errors were encountered: