NEW 31.1.2 versions keep crashing

[CarlSim]

all was fine until that new version... im on Kubuntu 24-04... was running ok until i add a web source. The youtube chat box started flikering then obs crashed...tried noumerous attemp to restart it,to remove that web source but no can do,obs crashes in few seconds.
Also,that fail safe mode doesnt work since its been added. I have a similar setup on my other computer and so far its ok.... My friend that runs about same thing YT stream) i am,also have problems since that new version came out,obs keep disconnecting.

i got lucky beeing fast enough on the mouse to delete the web source after 6-7 times and obs kept running after that.

o hope this will be fixed soon

 

[stephematician]

It _might_ be an issue with hardware acceleration. Go to "Settings", then "Advanced", then deselect "Enable Browser Source Hardware Acceleration"

If that works, then at least you have a workaround for now - but it could be a bug in the hardware acceleration that needs reporting.

 

[StrikerTheHedgefox]

Hardware acceleration made no difference for me. Anytime I edit a video source, there's a 50/50 chance it'll crash. This has been, by far, the most unstable release of OBS I've ever used.

 

[stephematician]

Hardware acceleration made no difference for me. Anytime I edit a video source, there's a 50/50 chance it'll crash. This has been, by far, the most unstable release of OBS I've ever used.

Could also try running with environment variable `QT_NO_GLIB=1`?

 

[deadmeu]

I updated the Flatpak recently and OBS now crashes for me as well. Not sure if it's OBS or KDE causing it:
```
PID: 79447 (obs)
UID: 1000 (user)
GID: 1000 (user)
Signal: 11 (SEGV)
Timestamp: Thu 2025-09-18 21:29:15 AEST (32s ago)
Command Line: obs
Executable: /app/bin/obs
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-flatpak-com.obsproject.Studio-1413663135.scope
Unit: user@1000.service
User Unit: app-flatpak-com.obsproject.Studio-1413663135.scope
Slice: user-1000.slice
Owner UID: 1000 (user)
Boot ID: ee715d086c854aaeb6382762bd6be630
Machine ID: 2e3d19c21e45452295221e20ded5ed92
Hostname: hostname
Storage: /var/lib/systemd/coredump/core.obs.1000.ee715d086c854aaeb6382762bd6be630.79447.1758194955000000.zst (present)
Size on Disk: 611.9M
Message: Process 79447 (obs) of user 1000 dumped core.

Stack trace of thread 128:
#0 0x00007f28d8060925 n/a (/usr/lib/x86_64-linux-gnu/libjack.so.0.3.1204 + 0x16925)
#1 0x00007f28d806747d n/a (/usr/lib/x86_64-linux-gnu/libjack.so.0.3.1204 + 0x1d47d)
#2 0x00007f2923f7d971 n/a (/app/lib/obs-plugins/linux-jack.so + 0x2971)
#3 0x00007f28d805fad8 n/a (/usr/lib/x86_64-linux-gnu/libjack.so.0.3.1204 + 0x15ad8)
#4 0x00007f28d8030755 n/a (/usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so + 0x9755)
#5 0x00007f28aa96af53 n/a (/usr/lib/x86_64-linux-gnu/libpipewire-0.3.so.0.1204.0 + 0x39f53)
#6 0x00007f2941699261 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x98261)
#7 0x00007f294171dd54 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x11cd54)
ELF object binary architecture: AMD x86-64
```

Also, my journal is spammed with the following (may be unrelated): `flatpak[82018]: 0548:err:seh:dispatch_exception assertion failure exception`

 

[stephematician]

@deadmeu - maybe don't use JACK audio sources then? Especially if you're running PipeWire, there's a plugin for talking to PipeWire directly instead of needing a JACK server (on top of PipeWire).

 

[deadmeu]

@deadmeu - maybe don't use JACK audio sources then? Especially if you're running PipeWire, there's a plugin for talking to PipeWire directly instead of needing a JACK server (on top of PipeWire).

If it's a plugin I may not have it since I'm using the Flatpak and plugins can be a little weird or difficult to add with it. For now, I reverted to version 31.0.4 (Flatpak commit caf0e8d12e2e072b8955a01815fac498746fd8da8de752f6d38a986fd5b21462) and it hasn't crashed so far, so I'm happy to just stay with on this version for now.

 

[stephematician]

If it's a plugin I may not have it since I'm using the Flatpak and plugins can be a little weird or difficult to add with it. For now, I reverted to version 31.0.4 (Flatpak commit caf0e8d12e2e072b8955a01815fac498746fd8da8de752f6d38a986fd5b21462) and it hasn't crashed so far, so I'm happy to just stay with on this version for now.

It is a plugin. There are instructions for using it with Flatpak in its GitHub README. Anyway, sound like you've got a solution that works for you anyway!