Bug Report OBS Studio not releasing resources on shutdown

Sean A McKinnon

New Member
Hello,

I have been having this issue for a while now. And in looking at other posts, I believe many others are having it and not realizing it is the same issue.

It appears that OBS Studio is not releasing resources after it is being closed. Specifically it does not terminate itself properly (obs32.exe continues to run in the backgrouns). It also does not terminate the Qt5Core.dll and cef-bootstrap.exe resources when it is closed. This causes them to continue running in the background using system resources without the user's knowledge or permission. This leads to issues when trying to install an update as those two files throw errors during installation since they are still running in the background. There should be absolutely no reason for these resources to continue running in the background after OBS Studio is closed.

The workaround is to open Task Manager (Ctrl-Shift-Esc) and manually end task on each of those 3 running processes. However this needs to be addressed so that OBS Studio properly cleans up after itself when it is closed/terminated.

Thank you for your time in reading this bug report. Hopefully it is addressed sooner rather than later.
 

Suslik V

Active Member
OBS Studio may stay in the memory only if you crashed. PC reboot is the better option in that case.
 

Sean A McKinnon

New Member
OBS Studio may stay in the memory only if you crashed. PC reboot is the better option in that case.
If it is due to a crash, it is not generating any kind of error messages when it happens. So how am I supposed to know that is the case.

I streamed the day before yesterday and closed OBS Studio down normally. When I went to install the latest update this morning, it was still running in the background. I had to use task manager to end the process before the install would go through. This has been going on for about a month now. Processes started by OBS Studio are not shut down properly. They continue to build up and use system resources until I am forced to either kill them in Task Manager or reboot my PC because they build up so many system resources over time that everything else slows down. And that's saying a lot since I have 32GB of memory.
 

Suslik V

Active Member
Studio has no build-in mechanism to restart after PC shutdown and startup. Are you using power saving options?
 

Sean A McKinnon

New Member
Studio has no build-in mechanism to restart after PC shutdown and startup. Are you using power saving options?
Apparently I didn't communicate myself properly. There is no PC shutdown and startup. I only shutdown or restart my PC when there are issues such as like what happens when OBS Studio doesn't properly end processes and they start using up a ton of system resources. I never said I expected it to restart after shutdown/startup/restart of the entire computer. I said after I CLOSE obs studio it doesn't properly dispose of background processes that start when you first launch it.

But you may be happy to know that I am now experiencing the crashing issues. I just got done tweaking some settings for my scenes in OBS and when I went to close it I got a message "obs64.exe has stopped working". Hopefully this gets hot-fixed in the very near future.
 

Suslik V

Active Member
Ja.., just give me more your crash logs ^_^

Can you post this one and other OBS Studio's crash logs if any?
 

Sean A McKinnon

New Member
Here is a copy of my most recent crash log from this morning. It does not appear to be holding onto those resources mentioned in my original post any longer. So that is a good thing. But it still crashes every single time I close it out after a stream.
 

Attachments

  • Crash 2016-08-13 10-10-18.txt
    50 KB · Views: 20

Sean A McKinnon

New Member
I figured it out. I had the Scene Switcher plugin installed. After removing it, the crash no longer occurs when I shut OBS Studio down.
 

Suslik V

Active Member
Please, re-post the logs to the Scene Switcher plugin thread if you think that it is related to your crashes.
 

dilydaly

New Member
I am still having this issue on a Windows 7 Laptop as of Aug 28, 2017. It started happening a month ago and now I can't get the program to shut down and properly release resources. Happens when I run both 32 and 64 bit, and when I encode using .avi and .mov.
 
Top