CasparCG crashes randomly on Ubuntu 24.04

General
1

Hi!

I’m having this issue with CasparCG crashing randomly with illegal instructions error.

/home/casparcg/run.sh: line 12: 2493 Illegal instruction (core dumped) LD_LIBRARY_PATH=“$BASE_DIR” “$BASE_DIR/casparcg-server-2.5” “$BASE_DIR/config/casparcg.config”

CasparCG crashed with code 132 — restarting in 2s…

Type “q” to close application.

Logging [info] or higher severity to log/

I tried many different approaches, fixes and builds and nothing seems to work. It happens on two different machines.
Does anyone have any idea what it is and how can i fix this?

2

How have you built this? have you tried with the deb packages?

Maybe your cpu doesnt support AVX2? The 2.5.0 release was built requiring that, but that has been stepped back in the not yet released 2.5.1 (but the beta builds of 2.5 on the website since then are updated)

3

I started with official deb package.
My cpu does support avx2. Checked it a couple times.
I went into a rabbit hole of trying to rule out its cef issues.
Tried also a build from source with the portAudio from GitHub - gmeisel01/server at portaudio-consumer · GitHub
The second machine is an older one so it could be missing avx2, but the one i’m using now is quite modern with i7-14700KF.

Now im testing on Ubuntu 26.04

Will try beta builds next

4

I can confirm now the crashes happen because of CEF. I did a fresh Ubuntu install, installed deb package of beta build 2.5.0 f517f48 Dev. Had it running all night with just videos, then in the morning i added some templates and in a couple minutes it crashed.
Does anyone have an idea what can i do to fix this?

5

I’m guessing your templates are using quite a lot of memory? It’s probably the same issue as this:

The tl:dr; seems to be to “build CEF without sysroot” (in an environment with glibc >= 2.33). …which is rather inconvenient for regular users of casparcg… I know of others that have done just that, and it resolved the issue for them. I’ll see if I can get hold of their cef build and how to make that available for you to test

6

Yes, that is exactly it. If you manage to get a build, that would be great.

I’ll get back to it next week.

The templates I use are mostly borders for PIP layers, will also try to check how memory hungry they are.

7

@Julusian How would we go about doing this? I can upload the custom built cef archive (it’s a drop in replacement for the “official” releases that we use, exact same version) to the dependencies releases. I’m not 100% sure what the consequences are if you try to run this build on a system with a glibc version earlier that 2.33, but from what I can tell, even ubuntu 22.04 came with a newer glibc than that.

Should I just replace the cef archive that we have, or should we provide som kind of “alternative cef” that you opt-in for via cmake options? I think it could be fine to try to just replace it. Ppl running the dev builds know what they are in for :slight_smile: