SceneSwitcher icon indicating copy to clipboard operation
SceneSwitcher copied to clipboard

1.19.2. crashes OBS 28.1.2 on Win10 x64

Open Fred-DTV opened this issue 3 years ago • 4 comments

Describe the bug The current release makes my OBS crash in multiple different ways. The 1.18 version works fine.

To Reproduce There are different scenarios in which OBS crashes, some of them are:

  1. Opening the advanced scene switcher settings
  2. Changing active media file (I have a media macro)
  3. Changing scene collections or any other ressource intense task (My PC is overpowered, so never had that)

Logs Logs are attached, however, this is really weird, because OBS doesn't give me a crash report in this case only the regular log file

adv-ss-Github2022.11.25.10.42.23.txt

2022-11-25 10-38-23.txt

Fred-DTV avatar Nov 25 '22 09:11 Fred-DTV

Thanks for reporting the issue! A similar problem was recently reported in #586.

Can you please test if the following build already solves the problem? https://github.com/WarmUpTill/SceneSwitcher/actions/runs/3517413978

WarmUpTill avatar Nov 25 '22 19:11 WarmUpTill

Hey Till

Unfortunately it still crashes :/

Fred-DTV avatar Nov 30 '22 10:11 Fred-DTV

Hi @WarmUpTill

After further testing I was able to find some more hints qhat could cause this:

  1. The problem seems to be an issue how the plugin uses the RAM. Everytime I am having the issue i can see how the RAM usage on my PC ramps up real fast all the way to the max of 64GB as soon as I hit the start button of the plugin.
  2. I was able to find the macro which includes the reason for this. It is the one with "any media in scene". I've attached my setup file.
  3. The media item seems to load a significant amount of memory when used. Even when just one media file is chosen for a trigger (no matter if "ended" or "time remaining shorter") It will already block a GB of RAM, for a video which is just a couple of seconds long. So I am assuming, that the "any media" option just loads all of the media items in at the same time, which causes the massive rise in RAM usage.

I hope you can work with this info

adv-ss-Downdays-2023.02.16.17.08.22.txt

EDIT: Tried it on all versions up to the 1.20.5

Fred-DTV avatar Mar 20 '23 11:03 Fred-DTV

Maybe it could be solution to go from "any" to "current playing" (there is a OBS variable for it) ?

Fred-DTV avatar Mar 20 '23 11:03 Fred-DTV