obsproject / obsproject/obs-studio
OBS Crashes when switching scenes by hotkey and an Image source file dialog box is open
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
Duplicated on Windows 11
OBS Studio Version
28.1.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/MAJHMyhbbbz2A56U
OBS Studio Crash Log URL
It didn't create a crash log.
Expected Behavior
- Select Scene containing an image source.
- In the "settings" area for the image source, select "Browse" (as in, browse for a new image).

- Do not select a file or close the file dialog box. Rather, use a hotkey to change to a scene that does not contain the image source.
- OBS should change to that scene. Wether or not the file browser window should remain open or functional is up to the OBS dev team
Current Behavior
- Select Scene containing an image source.
- In the "settings" area for the image source, select "Browse" (as in, browse for a new image).
- Do not select a file or close the file dialog box. Rather, use a hotkey to change to a scene that does not contain the image source.
- OBS crashes. Nothing appears in the logs. No crash report is generated.
Steps to Reproduce
- Create 2 scenes. In scene A, add an Image source. Do not add this source to scene B.
- Add a hotkey to change to scene B.
- Select scene A.
- Select the Image source in scene A.
- Click the "Browse" button to open the file dialog.

- While the file dialog is open, press the hotkey to change to scene B.
- OBS will crash, but nothing will appear in the logs and no crash report will be generated.
Anything else we should know?
I have replicated this on my desktop, too. It is much more powerful than my laptop (the desktop has an actual GPU, much more RAM, Windows 11, doesn't have any OBS plugins installed, etc), and the results are the same. It has completely different scenes, too, but the crash reliably happens from the same steps.
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 crash on Windows using the listed scene, Image source, Browse dialog, and scene-switch hotkey steps. Trace the Image source settings dialog while scene A is removed and verify that switching to scene B no longer crashes; the file dialog's behavior afterward is optional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100