OBS crashing nearly every time I switch scene Collections

flyinion

New Member
Just updated to 29.1.1 from 29.1 yesterday and all of a sudden I'm getting constant crashes any time I switch scene collections about 90% of the time. It complains about not being able to unload a plugin or something and to update them. The only plugin I know of I've been using is some VST plugins but I wasn't actually using them on my current mic. So with lots of crashes I managed to go through and remove it from all scenes but I'm still getting crashes. No idea why. I did add a stream deck a couple months ago with just some basic plugins in there which all seem to be up to date. Just the default "OBS Studio" plugin in it for switching scenes during a stream and for muting a mic source. I've never had any crashes like this before and have no idea what's going on. The only other thing I can think of is all my scenes and collections of them use Stream Elements for overlays but it looks like it's just a URL so I don't know what I could update there? I uploaded the log file here https://obsproject.com/logs/Q707ORGx3Hpa051e Starting to regret updating to 29.1.1 at this point.
 

PaiSand

Active Member
Turn off HAGS
Enable windows game mode.

 

flyinion

New Member
Turn off HAGS
Enable windows game mode.

Can't turn off HAGS, 4090 needs it to do Frame Generation.

edit: It also hasn't caused any issues until now, I wonder if an Nvidia driver update borked something.
 

flyinion

New Member
Anyone have any other idea besides gimping my GPU to try and fix this?

edit: Just to add info, I'm not streaming when these crashes occur. Literally just open OBS and switch collections (I have one collection per game streamed and sometimes copies of them to remove webcam and overlay for it)
 
Last edited:

R1CH

Forum Admin
Developer
That isn't a crash, that's an error message - very different things. As the message says, plugins are usually responsible for this issue as they hold onto sources from the current scene collection, preventing them from unloading when you try to switch collections. Update or remove any 3rd party plugins to see if it helps. Per the log file, something is affecting these sources in particular:

14:54:39.681: Not all sources were cleared when clearing scene data:
14:54:39.681:
14:54:39.681: - Yeti Mic
14:54:39.681: - Steelseries Mic
14:54:39.681: - Logitech webcam
 

flyinion

New Member
That isn't a crash, that's an error message - very different things. As the message says, plugins are usually responsible for this issue as they hold onto sources from the current scene collection, preventing them from unloading when you try to switch collections. Update or remove any 3rd party plugins to see if it helps. Per the log file, something is affecting these sources in particular:

14:54:39.681: Not all sources were cleared when clearing scene data:
14:54:39.681:
14:54:39.681: - Yeti Mic
14:54:39.681: - Steelseries Mic
14:54:39.681: - Logitech webcam
Well I tried the HAGS suggestion from the other person and definitely had no effect. I have no idea what would be affecting those. I have the Reaper VST plugins installed locally, but removed them from those sources in all my scene collections that I'm testing swtiching to and it's still doing it. I have zero plugins for the webcam. It's just using the built in crop/pad, color correction, and LUT filters

I keep getting this when switching the collections though and it's random both if it happens and which collections it happens between.
 

Attachments

  • OBS_issue.jpg
    OBS_issue.jpg
    27.3 KB · Views: 143

flyinion

New Member
The only other things I can think of that might affect any of those is the Blue Sherpa software for the Yeti to globally set the sound profile for it in any apps I'm using regardless of using OBS or not, and the Logitech Capture software to set focus/color temp settings each reboot since apparently Logitech cams don't remember that stuff in OBS but I didn't think those would be a "plugin" for example.
 

R1CH

Forum Admin
Developer
It's interesting that the sources that leak are all used in a scene-as-source scene. I wasn't able to reproduce that though when trying it myself.
 

flyinion

New Member
It's interesting that the sources that leak are all used in a scene-as-source scene. I wasn't able to reproduce that though when trying it myself.
They've been working fine until recently also, so it's weird. 95% sure this was not going on before I updated from 29.1 to 29.1.1. I wasn't streaming until this week since the end of March though and I thought I had 29.1 installed back then and it was totally fine. I tried to look through the logs but didn't know what to look for. I found some errors somewhere for my stream elements overlays so I don't know if something is up with their services causing something? I haven't made any recent changes to my overlays and they're very basic templates from SE anyway.
 

flyinion

New Member
It does seem like I'm now on some discontinued software though, looks like Blue Sherpa and Logitech Capture (used to set the camera settings on reboot) have all been merged to Logitech's GHub thing. Maybe I should try to migrate to that (don't have any other logitech devices so have been trying to avoid installing that).

Do you have those Reaper plugins installed anywhere? I know they were popular at one point and I had been using them when I was using the Steelseries headset mic before I got the Yeti X, but I don't use them now even though they're still installed. I see they haven't had an update since 2016 so I don't know if they're still affecting something. Like I said though I removed them from the mic sources in all the collections I've been testing swapping between to try and fix this so they should even be in use.
 

Suslik V

Active Member
Behavior is not related to the external utilities, it's for sure. Some internal OBS bug. I was able to reproduce this (but only twice) with empty sources and empty filters attached to them. In much older OS with very slow graphics, in VirtualBox environment. It will be hard to track the bug.
 

Attachments

  • 2023-05-12 12-38-07.txt
    12.9 KB · Views: 37

R1CH

Forum Admin
Developer
95% sure this was not going on before I updated from 29.1 to 29.1.1
There were some internal changes to sources that mean each source has a guaranteed unique id, even across scene collections. As part of this change, sources that remain after unload broke this system since switching scene collections and back again would cause two sources with the same unique ID to be loaded. The sources were still leaking in previous versions, it's just now a fatal error to prevent further weirdness or corruption when the same source is loaded twice as this is never expected to be possible.
 

flyinion

New Member
There were some internal changes to sources that mean each source has a guaranteed unique id, even across scene collections. As part of this change, sources that remain after unload broke this system since switching scene collections and back again would cause two sources with the same unique ID to be loaded. The sources were still leaking in previous versions, it's just now a fatal error to prevent further weirdness or corruption when the same source is loaded twice as this is never expected to be possible.
Ok, how can I fix this? Do I need to delete all my collections except say one and re-create? If so would I be able to do it the same way I originally did? Basically I originally set one up the way I wanted my base layout to be for any game I was going to stream. Then proceeded to duplicate it a few major versions ago and change the game capture for instance to a different game, give the duped collection a new name, etc. I've attached as an example how two of my collections look. obs_ex2.jpg was the original one that I based them all on.
 

Attachments

  • OBS_ex1.jpg
    OBS_ex1.jpg
    34.1 KB · Views: 78
  • obs_ex2.jpg
    obs_ex2.jpg
    43.9 KB · Views: 78

PaiSand

Active Member
Export the scene collections so you backup them. Then delete all. Restart OBS and start adding one by one testing in between.

Something in there is causing this:
14:54:41.725: Number of memory leaks: 2698
You need to identify where it is.
 

R1CH

Forum Admin
Developer
Export the scene collections so you backup them. Then delete all. Restart OBS and start adding one by one testing in between.

Something in there is causing this:

You need to identify where it is.
Memory leaks are expected when OBS shuts down after a reference leak.
 

BreeOge

New Member
This issue has made my OBS totally unusable! I am going to have to find a way to re-load the previous version, the newest is causing too many issues.
 

Suslik V

Active Member
I attached the latest contents of the "config" folder of OBS I tested (7z archive MD5:7bcd10ff8483e930afabe66f6e84f9c5 , maybe it will help to track the bug).
I run OBS (portable mode), and switched from the Scene Collection named "test_collection_switch_from" to the Scene Collection named "test_collection_switch_to". No other actions were made.
 

Attachments

  • 2023-05-14 12-24-04.txt
    13.2 KB · Views: 18
  • obs2_scene_collection_config_dir.7z
    645.5 KB · Views: 11

Suslik V

Active Member
Code:
12:45:00.213: ==== Shutting down ==================================================
12:45:00.241: All scene data cleared
12:45:00.242: ------------------------------------------------
12:45:00.342: Switched to scene collection 'test_collection_switch_from' (test_collection_switch_from.json)
Last message from the log-file may mislead - because I actually switched from the "test_collection_switch_from" scene collection. And all sources were gone (the Sources list cleared) when the error message risen. Thus, OBS was left on the scene collection "test_collection_switch_from", ready for the next startup.
 
Top