obsproject / obsproject/obs-studio
Crash if service restrictions change resolution and the user rejects changes
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 11
Other OS
No response
OBS Studio Version
32.1.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/crashes/0ivKCCEPMbyCs3IB
OBS Studio Crash Log URL
No response
Expected Behavior
Settings reverted.
Current Behavior
OBS crashes.
Steps to Reproduce
- Set output resolution to 4k
- Close settings
- Open settings
- Set service to Facebook, accept prompt about resolution change
- Close settings window
- Answer "No" to save settings prompt
Anything else we should know?
Presumably because the user never directly visited the Video settings page, the controls aren't valid, but LoadSettings tries to write to them as part of reverting the changes.
This pattern may also occur in other places where the code touches settings without user interaction.
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 reproducing the Windows 11 sequence in the issue and inspect the linked crash log. Trace the LoadSettings path used when rejecting the save prompt, especially after changing the service to Facebook without visiting Video settings; done means the settings revert completes without OBS crashing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100