obsproject / obsproject/obs-studio
Crash if you invoke GetOutputList via WebSocket under some conditions
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 76.4k
- Forks
- 10.2k
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 12
Description
Operating System Info
Windows 10
Other OS
No response
OBS Studio Version
31.0.0
OBS Studio Version (Other)
No response
OBS Studio Log URL
N/A
OBS Studio Crash Log URL
https://obsproject.com/logs/qMKTuld3G592YOZO
Expected Behavior
Not to crash
Current Behavior
Crashes
Steps to Reproduce
- Invoke GetOutputList when a profile change is occuring (I think)
- Crash
Using aitum:
- start main output
- start aitum outputs
- crash (on OBS inspecting the aitum output)
I've had this occur twice, the first time I wasn't sure when it was doing it
The second time it occur when I was making OBS change profiles.
I'm invoking GetOutputList every second, so theres a possible edge case where There are NO outputs (as it's rebuilding them) or things are occuring inside OBS meaning the outputs don't exist
Anything else we should know?
older log file:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the crash log and older crash log, then reproduce repeated GetOutputList WebSocket calls while changing profiles and starting the listed outputs. Trace what happens when outputs are being rebuilt or temporarily absent. Done means the reported sequence no longer crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100