Skip to content

eventhandler: Mark OBS as not ready during profile changes - #1366

Open
tt2468 wants to merge 1 commit into
obsproject:masterfrom
tt2468:fix/profile-change-not-ready
Open

tt2468 wants to merge 1 commit into
obsproject:masterfrom
tt2468:fix/profile-change-not-ready

Conversation

@tt2468

@tt2468 tt2468 commented Nov 1, 2026 •

Copy link
Copy Markdown
Member

Description

Consider OBS to be "not ready" while the profile is changing.

Motivation and Context

Certain requests like GetReplayBufferStatus can exhibit undefined behavior during profile changes. Rather than try to track down specific bugs there, we'll just play on the safe side and mark OBS as not ready.

How Has This Been Tested?

Tested?

Types of changes

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • I have read the Contributing Guidelines.
  • All commit messages are properly formatted and commits squashed where appropriate.
  • My code is not on master or a release/* branch.
  • The code has been tested.
  • I have included updates to all appropriate documentation.

Fixes #1365

Certain requests like GetReplayBufferStatus can exhibit undefined
behavior during profile changes. Rather than try to track down specific
bugs there, we'll just play on the safe side and mark OBS as not ready.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Crash in obs_frontend_get_replay_buffer_output when obs-websocket GetReplayBufferStatus arrives right after a profile reload

1 participant