Repository navigation
frontend: Abort if obs-transitions failed to load - #13321
Merged
Merged
Conversation
PatTheMav
reviewed
Apr 28, 2026
Warchamp7
requested changes
May 3, 2026
The frontend UI assumes transitions are always available and crashes if none are present. Resolving the crashes resulted in a completely broken UI, so it's safe to assume that transitions are a core requirement for a working OBS. Crash reports indicate that obs-transitions is failing to load for some users, so we should handle the case where no transitions load and abort with an error instead of crashing.
notr1ch
force-pushed
the
r1ch/transition-crash-fix
branch
from
May 5, 2026 21:55
88cf21a to
e943fd1
Compare
Warchamp7
approved these changes
May 6, 2026
PatTheMav
approved these changes
May 6, 2026
RytoEX
approved these changes
Aug 18, 2026
Warchamp7
added
the
release-note/fix
github-project-automation
Bot
moved this from Ready For Merge
to Merged
in 33.0 Release Tracker
2 of 20 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The frontend UI assumes transitions are always available and crashes if none are present. Resolving the crashes resulted in a completely broken UI, so it's safe to assume that transitions are a core requirement for a working OBS.
Crash reports indicate that obs-transitions is failing to load for some users, so we should handle the case where no transitions load and abort with an error instead of crashing.
Motivation and Context
https://obsproject.com/logs/crashes/09jMYJwaWSRscFNd
How Has This Been Tested?
Deleted
obs-transitions.dll, ran OBS.Types of changes
Checklist: