OBS Studio 32.1.0 crashes after shutdown

[MrDummyNL]

Operating System Info

Windows 11

Other OS

Windows 11

OBS Studio Version

32.1.0

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/2BUMxBeBRPW5lBi9

OBS Studio Crash Log URL

https://obsproject.com/logs/crashes/WQX05Dz2Lh91z1o3

Expected Behavior

Just close OBS again and it will always show crash message.
This happens ALWAYS no matter. Have not changed scenes.

The crash message window CANNOT closed, Yes an No buttons are not working.
Need go to Taskmanager to force close it.

Current Behavior

Crash every time when close OBS

Steps to Reproduce

1. Start OBS (with all scenes ofc)
2. Close OBS
3. Will throw crash window already.
   ...

Anything else we should know?

Previous versions have no crashes and all can shutdown without problems.
ONLY with version 32.1.0 i have crash problem. Earlier version no problem.

Here some look at scenes in this picture. Several browsers are open to run overlays.

Just close OBS and it will always show crash message.
This happens ALWAYS no matter. Have not changed layers.

The crash message window CANNOT closed, Yes an No buttons are not working.
Need go to Task manager to force close it. So it's another serious problem not be able close it.

Scenes changes are still saved, so it's at very end that makes it throw message.

I want roll back to previous version because this is nuts. No idea what changed but all previous versions have no problems.

[Sharkspi]

Hello I have the exact same issue and error in crash log.
Saw in some reddit posts a similar problem some times ago due to a websource, this might be due to the use of streamlabs but not sure. I tried to update SL plugin but the issue is still here.

[MysticalOS]

I'm also getting a shutdown crash every time. I also have a streamlabs web source, but i do not use their plugin, it's just an added source for chat and notifs

[prgmitchell]

@MrDummyNL you'll want to start OBS in safe mode when prompted and test again, this is likely a 3rd party plugin and you'd need to report directly to them if so.

[BenOravetz]

Just an update to this:

I had the same issue but I fixed it by disabling my StreamLabs plugin.

I will report that when the crash occurred for me, the crash dialog would freeze and I had to kill the process via Task Manager. That is probably not a plugin bug.

[MrDummyNL]

Before last version was out, i have no crashes.
Since last version, it throw always error after close OBS.

But if you say so, then it means StreamLabs need update the plugin. Many streamers still use StreamLabs and cannot just uninstall it.

[MysticalOS]

I don't actually have streamlabs plugin, just streamdeck and aitumsuite but disabling either of those isn't an option.

[Fenrirthviti]

Testing without third-party plugins enabled is critical to us being able to identify where the cause might be.

[MysticalOS]

The problem with aitum specifically is when you disable that plugin, every vertical scene gets converted to non vertical and it hoses tons of profiles. even when you re-enable plugin you basically have to scrap and redo every scene to fix it. Been through that once, never again.

That said, I actually did some more testing and i can open and close OBS as many times as I want and it will quit without crash even with plugins enabled, if it was only open a bit. but after a multi hour stream for example I quit same way, it hangs for a bit, then exits to a crash. so whatever cause is for me, it's something that accumulates over time.

[Fenrirthviti]

For future reference when doing testing, Scene Collections and Profiles are easily backed up from the respective menus.

However, we will likely need a dump file in order to identify what is going on. Anyone experiencing this specific crash should follow these steps:

https://obsproject.com/forum/resources/598/

Ensure that all the steps are read ahead of time, as they need to be strictly followed or the file will not be useful.

Once the dump file is acquired, do not post it publicly but reach out to myself on the OBS Discord, Fenrir (username len). I have DMs open.

Thank you in advance for anyone who is able to provide this.

[notr1ch]

Root cause: aboutToQuit handler triggering from a nested event loop (or just how Qt signals work?) and immediately calling obs_shutdown while a real shutdown from OBSBasic::~OBSBasic is already underway on the same thread.

CEF explodes because we're unloading obs-browser while there are still active CEF singletons.

[s1fat]

we need to fix that issue that happening for StreamlabsOBS extention that not happening in 32.0.4 verson that happening in new 32.1 and 32.1.1 version.

[daMoaT]

Ok, at 1st I was convinced this was due to the OBS background removal plugin, as I use an older version (1.1.13) as it allows me to use my AMD GPU for it, newer versions don't for some reason, but after unninstalling and reinstalling OBS, I'm now pretty sure that this crash is related to the Stream labs plugin, even though it auto updated when I launched OBS today... All other plugins except Streamlabs plugin were removed after unninstal/reinstall, and the crash remains, but after disabling Streamlabs plugin, the crash doesn't occur anymore.

Hope this helps to solve the crash, let me know if you want anymore details or want me to upload a crash log.

The crash doesn't look like a serious problem, as OBS doesn't even detect it crashed when I launch another session, it doesn't give the "OBS didn't shut down correcly, would you like to start in safe mode or normal mode" message, instead, it just looks like OBS is forcing the shutdown whilst some process is still running, likely streamlabs plugin.

[MysticalOS]

I get the shut down incorrectly error every launch, and I don't use streamlabs plugin. I think crash has numerous causes but is definitely a regression in 32.1.x

[MrDummyNL]

Got StreamLabs update some days ago and i have no more crashes, shut down correctly.
Hope others can fixed soon with last update.

[RytoEX]

@MrDummyNL glad to hear it.

@MysticalOS If I recall correctly, you're running macOS whereas the reporter is on Windows. I think there are subtle differences between the shutdown process between macOS and Windows, so I'm not sure if we should treat the original report the same as your case. @PatTheMav ?