obsproject / obsproject/obs-studio
Mac mystery crash: variety of routes
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 76.4k
- Forks
- 10.2k
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 12
Description
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/jXG3oBflx2TT2VNY
OBS Studio Crash Log URL
No response
Expected Behavior
Not to crash with a Problem Report when invoking various functions not from the UI (Streamdeck/Websocket being not from the UI)
Including but not limited to:
- Just connecting a websocket
- Getting the list of profiles (GetProfileList)
- Changing the currently active profile
- Updating various parameters on the current profile via
SetVideoSettingsand/orSetProfileParameter, but I suspect here OBS segfaulting at the Get/Set Profile I do before this call which is what other things/application do to cause the crash (streamdeck/OBS Blade)
Current Behavior
Crashes with a problem report
Steps to Reproduce
Method 1:
- Using the streamdeck and it's plugin switch between profiles a number of times (it's not directly tied to speed of switching aka spamming switching), not sure what mechanism is used under the hood there.
Method 2:
- Using the websocket switch between profiles a number of times
Method 3:
- Using the websocket under the currently selected profle
- Call GetProfileList
- Then it crashes
Some of these methods are inconsistent/not 100% reliable to trigger, but I also did a full nuke of OBS from my mac and did a fresh grab of latest release and same issue presents: IE no extra plugins installed beyond activating the WebSocket.
Sometimes Mac OBS will also crash the moment I connect a websocket. At identify I'll call "GetProfileList" as the first call.
In the last round of testing I have no sources in the only source collection either.
It also behaves similar on the RC1 of 30.2.0
And I have a report that it occurs on another users machine with release and OBS Blade (a seperate controller), granted blade also uses the websocket socket, it just rules out my code being at fault)
Doing the same "dumb shit" (if you pardon the expression) on windows cannot replicate the fault, so it seems localised to the mac version of OBS
Anything else we should know?
Mac Problem report for OBS Studio, The problem report is longer than 65536 chats so I've uploaded it to my pastebin https://pastebin.com/PFB1Rqmy
A second problem report https://pastebin.com/gzZRBmVc
It's OBS Log file https://obsproject.com/logs/kAjQ3olT5TOkyNmY
After doing a few profile changes via a WebSocket control
Yes it's a not normal aspect ratio here but I can cause the problem from just switching between a bunch of normal aspect ratio profiles, the profile I'm working with primarilly is for a vertical streaming platform, but I don't think that matters here
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the OBS log URLs and the two macOS problem reports, then reproduce the crash through WebSocket profile operations such as GetProfileList and profile switching. Done means the reported macOS workflows no longer crash, including repeated profile changes and connecting a WebSocket.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, macos
- Domain
- api, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100