OBS crash when Advanced Scene Switcher is active, Streaming and Recording at the same time

[doswaldtaco]

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

32.1.0-rc4

Advanced Scene Switcher Version

1.32.8

Plugin settings

Download "Macros.txt" and "adv-ss-Default-2026.03.13.21.41.31.txt" from the "Steps to Reproduce" section below

OBS Studio Log URL

https://obsproject.com/logs/v91D7fY4zH74lXNq

OBS Studio Crash Log URL

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

Expected Behavior

I expect to be able to stream and record at the same time while my Advanced Scene Switcher macros are running.

Current Behavior

OBS works as expected when any 2 of the following 3 scenarios are true:

• Advanced Scene Switcher is Active
• Recording (native) is Running - Non-native recording, such as using the "Branch Output" plugin, works fine
• Stream (native) is Running - I have not tested it, but I suspect that non-native streaming using a plugin, such as "OBS Multi-RTMP," will work fine, too.

However, when all 3 are true at the same time, OBS will abruptly force close (usually within 30 seconds, but my longest test did so in 86 seconds) without providing any user-facing error messages.

Steps to Reproduce

1. Import my Macros.txt into Advanced Scene Switcher and ensure the plugin is currently "Active." Here are my settings if needed: adv-ss-Default-2026.03.13.21.41.31.txt.
2. Start a stream using the native OBS function
3. Start a recording using the native OBS function
4. OBS will crash within a couple minutes (about 5-90 seconds in my testing)

Anything else we should know?

I suspect that it may have something to do with my "Variables" and "Chapter markers" macros, and/or the frequency of condition checks (300ms) in general.

I've also tried stress testing a stream with Advanced Scene Switcher active for 40 minutes while overloading my encoder (recording using Branch) and OBS was stable the entire time. However, after activating the native OBS recording so all 3 conditions were True, it crashed within 10 seconds. My normal stream would not be this intensive, and I tried to generate a log of a typical setup for this report, so I don't think that test will be present.

Finally, I've removed my Twitch connection for the Advanced Scene Switcher settings export, but I normally have them populated.

[WarmUpTill]

Thanks for reporting the issue!

Did you accidentally upload the wrong crash report?
The one attached here points to the stream deck obs plugin (streamdeckpluginobs32.dll) as the cause of the crash:

Thread 14327C: tiny_tubular_task_thread (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000CB9D3FF360 00007FF99A3696C7 0000000000000000 00007FFA00000000 00000203D555BA60 0000000000000000 streamdeckpluginobs32.dll!0x7ff99a3696c7
000000CB9D3FF490 00007FF99A36D94F 00000203D555BA60 00000203D5557840 0000020408E99700 000000CB9D3FF4E0 streamdeckpluginobs32.dll!0x7ff99a36d94f
000000CB9D3FF550 00007FF9E9E28772 00000204A3E96A20 00007FF9E9E64FC8 000000CB9D3FF5F0 0000000000000000 obs.dll!signal_handler_signal+0x122
000000CB9D3FF5D0 00007FF9E9DE0E5C 0000000000000000 00000203D5557840 0000000000000010 00000203D5557840 obs.dll!obs_source_dosignal+0x17c
000000CB9D3FF6E0 00007FF9E9DE6F69 00000203D5557840 00000203D5557840 000002040805DAA0 00007FF9E9DE6F20 obs.dll!obs_source_destroy_defer+0x49
000000CB9D3FF730 00007FF9E9E246A4 0000000000000000 FFFFFFFFFFFFFFFF 000000CB9D3FF7F0 00000203D5565610 obs.dll!tiny_tubular_task_thread+0x434
000000CB9D3FF790 00007FFA0B6A1461 00000203D5415160 0000000000000000 0000000000000000 0000000000000000 w32-pthreads.dll!ptw32_threadStart+0x171
000000CB9D3FF800 00007FFA36AD37B0 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ucrtbase.dll!0x7ffa36ad37b0
000000CB9D3FF830 00007FFA3840E8D7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ffa3840e8d7
000000CB9D3FF860 00007FFA3960C53C 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffa3960c53c

[doswaldtaco]

Thanks for the quick reply! I guess it didn't cross my mind to look at the crash log I uploaded because there was no "view online" button like there is for the regular log.

Anyway, I just tried disabling the Stream Deck plugin and reproducing the error, but instead of it working for a few seconds and then crashing like it always has, OBS immediately froze for about 30 seconds and then finally crashed to desktop. I then went into the crash log folder and see that no logs are being generated when this problem happens. The "Crash 2026-01-28 23-36-37.txt" I uploaded is the last crash log that's being created (the regular OSB log is current, however).

I tried running OBS as an administrator and that didn't help create a log. Also, as expected, running OBS in safe mode didn't cause the crash, but neither did disabling only Advanced Scene Switcher from my plugins list (screenshot below).

I'll continue testing and see trying to generate a log in the meantime.

[doswaldtaco]

Hi, I've found out exactly what is causing my crash (I'm still unable to produce a crash log, though). The revised conditions for replicating this crash are:

1. Make Advanced Scene Switcher check conditions every 10ms-2000ms - I need it to be around 10ms because I'm recording time (though could possibly go as high as 60ms), but I also crashed it at 2,000ms before skipping to the max of 20,000ms, which I was not able to make crash. However, those are far beyond the range of what I can use.
2. Start a Stream - I used a OBS Bitrate Test Mode / Twitch Inspector so I wouldn't go live
3. Start a Recording
4. Enable both my "Recording" and "Streaming" macros - Here is an export of all related macros for my use case below: Macros 2026-03-22.txt (it doesn't matter if the other macros are enabled or not to reproduce this crash)
5. OBS should crash either immediately, or within a couple minutes.

The Recording and Streaming macros are used together with the Date and Time and Chapter markers macros to create a log for reviewing or adding to the YouTube video's description. Here's an example of the file that is created with these 3 macro sets enabled: Chapter markers.txt

I'm guessing that there is a conflict/overload that prevents AdvSS from simultaneously reporting the stream and recording duration based on the fact that I couldn't get it to crash with a high enough condition check time. If my crash is not being caused by a bug in AdvSS, then is there a way to fix or simplify my "Variables" macros to make them more efficient in generating the timestamps I need?

[WarmUpTill]

Thanks for the updated instructions!

I can confirm that I am able to reproduce the crash.
I will let you know once I know more about the root cause or if I have a fix.

[WarmUpTill]

I think I was able to track down the problem.
It was related to parallel executions of the "math" option of the "Variable" action.

A build with a fix will be available here in a few minutes:
https://github.com/WarmUpTill/SceneSwitcher/actions/runs/23554178871

Let me know if that solves the issue on your side.

[doswaldtaco]

This version appears to fix the crash. I just ran the new version for over an hour and had no issues at all!

Thank you!