You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think those OBS logs will be super useful -- I looked at all my logs and they don't seem to have anything related to the crash.
I also found making a more than few websocket requests back to back consistently creates bad Untitled.json files which cause my OBS to crash on startup.
Current Behavior
OBS crashes on startup with seemingly no relevant logs.
Steps to Reproduce
I got here from programmatically making a number of (valid) websocket requests, but I found I the source of. the crash to be in the Untitled.json that OBS created.
Starting from a fresh install
Open OBS so files in ~/Library/Application Support/obs-studio/ are created
Replace ~/Library/Application Support/obs-studio/basic/scenes/Untitled.json with the following contents:
macOS application crash logs are handled by macOS and available on application crash or via Console.app.
Open Console.app (Located in /Applications/Utilities).
Navigate to the Crash Reports view along the left sidebar, then sort the table by date to find the most recent crash with the OBS process name.
Drag and drop the selected crash onto the comment box to upload the file, or zip it and upload it, or copy-and-paste the report text here.
Strangely, this crash looks like it occurs within obs-websocket itself. Worth noting that this does not cause a crash on Windows. However, since there are no scenes defined in the scene collection, nothing is displayed.
The key here seems to be that there are no scenes in the scene collection file, which causes a crash deep in obs-websocket/nlohmann-json/stdlib when trying to get the name of the current scene (there is none).
Operating System Info
macOS 14
Other OS
No response
OBS Studio Version
30.1.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/PoDNSobWHFldo2Nz
OBS Studio Crash Log URL
No crash logs generated
Expected Behavior
OBS not to crash on startup.
I don't think those OBS logs will be super useful -- I looked at all my logs and they don't seem to have anything related to the crash.
I also found making a more than few websocket requests back to back consistently creates bad
Untitled.json
files which cause my OBS to crash on startup.Current Behavior
OBS crashes on startup with seemingly no relevant logs.
Steps to Reproduce
I got here from programmatically making a number of (valid) websocket requests, but I found I the source of. the crash to be in the
Untitled.json
that OBS created.~/Library/Application Support/obs-studio/
are created~/Library/Application Support/obs-studio/basic/scenes/Untitled.json
with the following contents:Anything else we should know?
No response
The text was updated successfully, but these errors were encountered: