31.0.0 freezes when exiting on macOS

[izwb003]

Operating System Info

macOS 15

Other OS

No response

OBS Studio Version

31.0.0

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/BQZ9q616XlYA2vgE

OBS Studio Crash Log URL

No response

Expected Behavior

OBS can quit normally every time and will not display the safe mode dialog on next startup.

Current Behavior

Sometimes (frequently) OBS will freeze on quit.

Steps to Reproduce

1. Launch OBS 31.0.0 (both tried in normal mode and safe mode);
2. Do something or not;
3. Quit OBS, then it freezes, macOS beachball appears;
4. Force to quit and launch again, OBS will ask me to choose running in safe mode or normal mode;

Anything else we should know?

Other users have also reported this issue, see the forum, which seems to only occur in OBS 31.0.0 version. This issue will occur regardless of whether the program is started in safe mode or not. The above log was recorded in safe mode, and it seems that it did not record any issues.

I also discovered that if this issue occurs, OBS will not be able to show any window and will not display any pop-up menus except the settings window. But when I open the settings or click the OBS icon on the dock, these windows will appear again. OBS will also freeze if I try to switch between Profiles or Scene Collections.

[morningwind128]

me too!

[jcm93]

Could you please collect a Spindump while OBS is in the unresponsive state?

Specifically, you'll want to select OBS in the list of applications in Activity Monitor (it should say "Not Responding"), then hit the ellipsis and Spindump. Then when the file pops up in Finder, attach it here.

[izwb003]

Could you please collect a Spindump while OBS is in the unresponsive state?

Sure. Here is it:
OBS_issue_11650_spindump.txt
And here is how it is symbolized with dSYMs, if no mistake:
OBS_issue_11650_spindump_symbolized.txt

[jcm93]

Thanks; it looks like a deadlock between the destruction task queue and the main thread. I can't tell exactly why it's happening though at the moment and am not able to reproduce. If other users have a Spindump (accompanied by an OBS log) that would still be useful to perhaps identify a common factor.

[izwb003]

Thanks; it looks like a deadlock between the destruction task queue and the main thread. I can't tell exactly why it's happening though at the moment and am not able to reproduce. If other users have a Spindump (accompanied by an OBS log) that would still be useful to perhaps identify a common factor.

It sounds like a problem that can only be replicated on some devices. Perhaps we need to wait for more reports from users.

Since my device can reproduce the issue, will it help identifying the cause if I try to build from the source for debugging?

[Kinfxhk]

me2 , using mac mini