Segfault on Debian when closing dialog box about sceneswitcher HOT 15 CLOSED

Thanks for letting me know about this!

Did this start to happen recently? (maybe with OBS 26?)
Does the issue also show with previous versions of the plugin?

It sounds like the main thread of the plugin cannot start for some reason.

Edit: Do you see more output of the scene switcher if the verbose logging is enabled on the general tab?

from sceneswitcher.

I have the latest OBS, and I only just got the plugin today from the OBS Forums page, I'll get some more info on verbose logging/old versions etc. tomorrow when I'm at my PC again!

from sceneswitcher.

Just a small update:

Good news.
The issue is easily reproduced in a VM.

Bad news.
All the UI connections seem to randomly assigned to unexpected other events.
For example "Switch to any scene on random tab" is replacing the start / stop button.
Even recompiling it in the Debian 10 environment leads to the same behaviour.

Unfortunately I have no clue yet what might be causing this so I cannot really say when I will get around to fixing this behaviour.

While previous versions of the plug in do not crash they unfortunately show the same behaviour of the strange UI connections.
So while you could potentially use older versions of the plug it might be very frustrating to use.

I assume this problem has existed for a while but no one reported it yet.

from sceneswitcher.

from sceneswitcher.

Okay, so having a look at the older versions, it appears that 1.6.2 doesn't crash OBS when the dialog box is closed, and this is the same for all versions of SS from 1.4. However, the start button doesn't work for any of these versions either. It appears that only the latest version, 1.7, crashes OBS on dialog closure, but the start button still doesn't work.

Hopefully this helps in solving the problem!

from sceneswitcher.

Thanks for the tests!

However, the start button doesn't work for any of these versions either.

That is what I meant with "it might be very frustrating to use." :)

You could try using the hotkeys to start the scene switcher or use "Switch to any scene on random tab" as the start button, as that is for some reason linked to that functionality on Debian 10.
But I can of course not say if there are any other unexpected side effects.
Also maybe the plugin "source switcher" could be used for your intended use case instead?

Unfortunately I still have not found the root cause.

from sceneswitcher.

I see what you mean now! Assigning a hotkey to toggle SS works perfectly, so I'm glad it's (mostly) working now. There doesn't appear to be any other issues asides from the start/stop button not working, and the dialog crashing OBS in the newest version, which is good.

Of course there's no rush in determining the root cause (though I'm sure others would appreciate it!) seeing that there's a workaround, and as long as I can get the plugin to do what I need, that's perfect 😄

from sceneswitcher.

Just for your information:
It seems to be a conflict with the frontend tools.
Removing them solves all of the strange behaviour, but will of course leave you without these tools.

I will try to find out what exactly the issue is on the weekend.

from sceneswitcher.

from sceneswitcher.

So it looks like the main issue was that the main widget of the scene switcher UI was named "SceneSwitcher", which the built-in scene switcher is, too.

I changed the name of this widget with 986422c.

You can find a build with this change here in a couple of minutes:
https://github.com/WarmUpTill/SceneSwitcher/runs/1271493529

I would appreciate if you could also confirm this on your end.

I still do not understand why this is only an issue on Debian 10, but for now the problem should be solved.

from sceneswitcher.

Hi! Good to hear that you've found a potential cause for the issue. Unfortunately I'm not at my main PC for some time as I'm away right now, but I thought I'd do a test on my Chromebook which allows Linux apps to run in a Debian 10 container as part of Chrome OS's Crostini. As you should imagine, running this sort of stuff in a container is a bit buggy (namely OBS having quite a few rendering bugs), but this is what happens when I interact with SceneSwitcher:

https://www.loom.com/share/01cc55fc1a9c465ab970f39f10236e0d

There seems to be some strange behaviour which sometimes happens when switching to different tabs in SceneSwitcher, as you should observe in the video I posted above. On some occasions, SceneSwitcher randomly jumps to the Transition tab instead of the General tab, sometimes on startup but also when you interact with the dialog (as shown in the video). Then, when I do get to the General tab, clicking the start button strangely crashes OBS. Here's a log (the same one that was in my terminal in the video):

Fontconfig error: "/home/jamesliveg/.config/fontconfig/fonts.conf", line 10: junk after document element
Attempted path: share/obs/obs-studio/locale/en-US.ini
Attempted path: /usr/share/obs/obs-studio/locale/en-US.ini
Attempted path: share/obs/obs-studio/locale.ini
Attempted path: /usr/share/obs/obs-studio/locale.ini
Attempted path: share/obs/obs-studio/themes/Dark.qss
Attempted path: /usr/share/obs/obs-studio/themes/Dark.qss
info: CPU Name: 06/8e
info: CPU Speed: 1607.952MHz
info: Physical Cores: 1, Logical Cores: 2
info: Physical Memory: 6639MB Total, 495MB Free
info: Kernel Version: Linux 5.4.58-07649-ge120df5deade
info: Distribution: "Debian GNU/Linux" "10"
info: Window System: X11.0, Vendor: The X.Org Foundation, Version: 1.20.8
info: Portable mode: false
QMetaObject::connectSlotsByName: No matching signal for on_advAudioProps_clicked()
QMetaObject::connectSlotsByName: No matching signal for on_advAudioProps_destroyed()
QMetaObject::connectSlotsByName: No matching signal for on_program_customContextMenuRequested(QPoint)
info: OBS 0.0.1 (linux)
info: ---------------------------------
info: ---------------------------------
info: audio settings reset:
        samples per sec: 44100
        speakers:        2
info: ---------------------------------
info: Initializing OpenGL...
info: Loading up OpenGL on adapter Red Hat virgl
info: OpenGL loaded successfully, version 4.3 (Core Profile) Mesa 19.2.8, shading language 4.30
info: ---------------------------------
info: video settings reset:
        base resolution:   1332x889
        output resolution: 1064x710
        downscale filter:  Bilinear
        fps:               30/1
        format:            NV12
        YUV mode:          601/Partial
info: Audio monitoring device:
        name: Default
        id: default
info: ---------------------------------
info: [adv-ss] trying '/home/jamesliveg/SceneSwitcher/bin/64bit'
info: [adv-ss] trying '/usr/lib'
info: [adv-ss] trying '/usr/local/lib'
info: [adv-ss] trying '/usr/lib/x86_64-linux-gnu'
info: [adv-ss] found curl library at '/usr/lib/x86_64-linux-gnu/libcurl.so.4'
info: [adv-ss] curl loaded successfully
libDeckLinkAPI.so: cannot open shared object file: No such file or directory
info: No blackmagic support
info: VLC found, VLC video source enabled
info: ---------------------------------
info:   Loaded Modules:
info:     vlc-video.so
info:     text-freetype2.so
info:     rtmp-services.so
info:     obs-x264.so
info:     obs-transitions.so
info:     obs-outputs.so
info:     obs-filters.so
info:     obs-ffmpeg.so
info:     linux-v4l2.so
info:     linux-pulseaudio.so
info:     linux-jack.so
info:     linux-decklink.so
info:     linux-capture.so
info:     linux-alsa.so
info:     image-source.so
info:     frontend-tools.so
info:     advanced-scene-switcher.so
info: ---------------------------------
info: ==== Startup complete ===============================================
error: Service '' not found
info: All scene data cleared
info: ------------------------------------------------
info: pulse-input: Server name: 'pulseaudio 12.2'
info: pulse-input: Audio format: s16le, 48000 Hz, 2 channels
info: pulse-input: Started recording from 'alsa_output.hw_0_0.monitor'
info: pulse-input: Server name: 'pulseaudio 12.2'
info: pulse-input: Audio format: s16le, 48000 Hz, 2 channels
info: pulse-input: Started recording from 'alsa_input.hw_0_0'
info: Switched to scene 'Scene'
info: ------------------------------------------------
info: Loaded scenes:
info: - scene 'Scene':
info:     - source: 'Color Source' (color_source)
info: - scene 'Scene 2':
info: ------------------------------------------------
info: adding 23 milliseconds of audio buffering, total audio buffering is now 23 milliseconds
info: adding 46 milliseconds of audio buffering, total audio buffering is now 69 milliseconds
qt.svg: Cannot open file '/home/jamesliveg/forms/images/up.svg', because: No such file or directory
qt.svg: Cannot open file '/home/jamesliveg/forms/images/up.svg', because: No such file or directory
qt.svg: Cannot open file '/home/jamesliveg/forms/images/down.svg', because: No such file or directory
qt.svg: Cannot open file '/home/jamesliveg/forms/images/down.svg', because: No such file or directory
error: X Error: BadAtom (invalid Atom parameter), Major opcode: 20, Minor opcode: 0, Serial: 11
error: X Error: BadAtom (invalid Atom parameter), Major opcode: 20, Minor opcode: 0, Serial: 15
error: X Error: BadAtom (invalid Atom parameter), Major opcode: 20, Minor opcode: 0, Serial: 19
info: adding 23 milliseconds of audio buffering, total audio buffering is now 92 milliseconds
info: [adv-ss] started
Segmentation fault (core dumped)

Bearing in mind that this is a fresh OBS install with the particular build of SceneSwitcher from the GitHub Actions run you posted. I would think that the issues shown in the video only happen on Crostini, considering that running Linux apps on Chrome OS is pretty unstable. But since you managed to reproduce the original issue in a Debian VM, I'm assuming it works at your end now?

I'll let you know if the build works for me when I'm back at the PC (in a few weeks time)!

from sceneswitcher.

Thanks for the test and the video!

Unfortunately the build I sent you could be a bit unstable as it is from a branch in with a lot of changes regarding the UI (unrelated to the original problem you encountered).
Although this behavior very surprising as I did not touch the tab widget.

I'm assuming it works at your end now?

While I did not do extensive testing I could no longer observe the original issue of the built in scene switcher of OBS conflicting with the plugin.

Anyways I will try to reproduce the problem shown in the video on my end and let you know once I find anything.

from sceneswitcher.

from sceneswitcher.

Were you already able to check if the crashes still happen on your main PC setup?

from sceneswitcher.

I can confirm that the build from 986422c works perfectly on my PC! Everything works without any crash ─ the dialog closes correctly and the start/stop button works as intended. 👍

Thanks for the fix! And also a great project; looking forward to future updates!

from sceneswitcher.