You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Create a new Scene via the Websocket API (CreateScene)
Make the newly created scene the active scene via the API (SetCurrentProgramScene)
Remove All Scenes via the Websocket API (GetSceneList -> RemoveScene)
Create a new scene using the same name used in (1) via the Websocket API (CreateScene)
I've got a minimal golang program that reporduces this issue below, hopefully that is all you need to reproduce this.
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.
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: