New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Websocket API crash and settings corruption when recreating active scene #10533
Comments
FYI, I have reported a separate but similar bug to this one ( #10532 ). I'm mentioning it as they may share a common underlying cause. |
A comment in the other bug report I submitted (#10532 (comment)) suggested adding a delay after calling RemoveScene, to determine if a race condition was occurring. While it had no impact in that issue, when applying a 500ms delay to the call in this issue it resulted in the crash no longer occurring, and the final CreateScene call works as expected. |
Having a similar issue via the websocket API on MacOS |
Operating System Info
Windows 11
Other OS
No response
OBS Studio Version
30.1.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/FHZeBkwviLAZ7XnQ
OBS Studio Crash Log URL
https://obsproject.com/logs/cGfkBclwG4JMzIeP
Expected Behavior
No crash or settings corruption should occur.
Current Behavior
When calling CreateScene via the Websocket API using the name of the previously active scene that has just been deleted, a fatal crash occurs.
Then further crashes occur on OBS startup until the %APPDATA%/basic settings directory is deleted.
Steps to Reproduce
I've got a minimal golang program that reporduces this issue below, hopefully that is all you need to reproduce this.
Anything else we should know?
No response
The text was updated successfully, but these errors were encountered: