OBS does not exit cleanly. The process is left running in the background and I must use Task Manager to manually kill the process before I can launch the program again. Only one recording session is possible until I exit the program, manually kill the process and then restart. Is this a know bug?? Is there a fix??
OBS Does not exit correctly, leaves process running, must be killed manualy.
- Thread starter ppat9
- Start date
Here is the log file. https://obsproject.com/logs/diNJyGrl5aJzon2x
dqm
Member
I've had same problem on more than one Windows 10 platform for some time. Regardless of how I exit OBS, processes accumulate and are visible in task manager with 0% cpu. They haven't prevented me from restarting OBS, but they do prevent applying updates, including windows maintenance at times
Lawrence_SoCal
Active Member
This is NOT my area of expertise, but from almost 2 years on this site, I can say with high confidence that the vast majority of the time, the issue is NOT OBS, but rather 3rd party plugins or user error in custom recording settings
Combine that with the recent OBS v27.2.x update swapping out the underlying OBS Browser (Chromium) which many plugins were using, and no surprise that plugins will need an update
And some plugins (like streamelements) are written much more poorly than others. Some replace core OBS components, which can cause all kinds of havoc (stupid streamelements). Anyway, some plugins, you can simply disable/uninstall and test. Others require a removal, clean, and re-install of OBS to fix plug-in caused bugs (nothing OBS can do about it/fix. issue is plugin)..
The other common big crash issue (but not causing the process hang as mentioned) is graphics drivers.
I can't say in your case which is root cause. To troubleshoot on your own, I would suggest trying to install OBS in portable mode to get a clean OBS only instance and test there. If that is stable, there is your answer [not OBS's fault]. I suggest separate instance/portable mode to quickly do a clean test and not require a significant amount of effort with OBS removal, clean up, and re-install.
Good luck
Combine that with the recent OBS v27.2.x update swapping out the underlying OBS Browser (Chromium) which many plugins were using, and no surprise that plugins will need an update
And some plugins (like streamelements) are written much more poorly than others. Some replace core OBS components, which can cause all kinds of havoc (stupid streamelements). Anyway, some plugins, you can simply disable/uninstall and test. Others require a removal, clean, and re-install of OBS to fix plug-in caused bugs (nothing OBS can do about it/fix. issue is plugin)..
The other common big crash issue (but not causing the process hang as mentioned) is graphics drivers.
I can't say in your case which is root cause. To troubleshoot on your own, I would suggest trying to install OBS in portable mode to get a clean OBS only instance and test there. If that is stable, there is your answer [not OBS's fault]. I suggest separate instance/portable mode to quickly do a clean test and not require a significant amount of effort with OBS removal, clean up, and re-install.
Good luck