Tanker
Members
-
Joined
-
Last visited
Solutions
-
Tanker's post in "segfault at 330 ip... error 6 in libavcodec" error help was marked as the answerAfter lots of testing and messing with chat GPT, I seem to have identified the issue and fixed it.
I had a script to ffprobe all my media which flagged 8 files that were bad, but the issue persisted even after removing those.
Then had a script to watch the ffprobe segfaults and determine which container was sending reports.
Bazarr was the container sending the segfaults and it looks to have stemmed from an older version of ffmpeg with older codecs.
installed a separate ffmpeg and mapped a path for Bazarr and so far it seems to be working with no errors.
Hopefully this helps someone in the future if they ever get a similar issue.