For the VLC case (only when actually starting a video) $ vlc VLC media player 2.1.4 Rincewind (revision 2.1.4-0-g2a072be) [0x138d148] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. *** Error in `vlc': free(): invalid pointer: 0x00007f3fe4ec09f8 *** Mplayer had similar issues, but I fixed that one by simply recompiling, which probably works for the VLC case as well, but going to leave that one the way it is for now. Reproducible: Always
... If such problem happened in mplayer and recompiling was *actually* the thing that fixed it, it would suggest an ABI break took place, but upstream failed to bump library names. So, please retest.
Well, recompilation of vlc *actually* fixed it.
totem dummy.avi ERROR: Caught a segmentation fault while loading plugin file: /usr/lib64/gstreamer-1.0/libgstlibav.so Please either: - remove it and restart. - run with --gst-disable-segtrap --gst-disable-registry-fork and debug.
...:sigh:... libgstlibav.so isn't totem - it's media-plugins-libav ...and again it seems ffmpeg upstream (interesting question: libav too ?) broke ABI, but didn't bump libraries.
...*media-plugins/gst-plugins-libav*...bah...
http://upstream-tracker.org/versions/ffmpeg.html
Hit a similar issue here too (same deal as bug 518356, gst-plugins-ffmpeg). Agreed that these two bugs probably stem from the same issue.
*** Bug 519664 has been marked as a duplicate of this bug. ***
Guessing this needs sub slot operators such that reverse dependencies rebuild.
(In reply to Tom Wijsman (TomWij) from comment #9) > Guessing this needs sub slot operators such that reverse dependencies > rebuild. Pretty much what I've already written - the subslot is based upon library versions and upstream failed to bump those when they've broken ABI.
(In reply to Tom Wijsman (TomWij) from comment #9) > Guessing this needs sub slot operators such that reverse dependencies > rebuild. eww no, offending packages need to be fixed; this is likely due to deprecated usage of ffmpeg api
(In reply to Alexis Ballier from comment #11) > eww no, offending packages need to be fixed; this is likely due to > deprecated usage of ffmpeg api For VLC, comment #2 rules that out; deprecated usage doesn't allow recompilation.
(In reply to Tom Wijsman (TomWij) from comment #12) > (In reply to Alexis Ballier from comment #11) > > eww no, offending packages need to be fixed; this is likely due to > > deprecated usage of ffmpeg api > > For VLC, comment #2 rules that out; deprecated usage doesn't allow > recompilation. did you have a look at the code ? what I've seen is an AVFrame allocated on the stack while the API is clear that it should use ffmpeg's provided allocator. with refcounted frames, guess what happens when it automatically freees it.
(In reply to Alexis Ballier from comment #13) > did you have a look at the code ? No, there is no need for it; not a code problem, because a rebuild suffices.
I thought the maintainers already knew... FF_INPUT_BUFFER_PADDING_SIZE has been changed. Due to the heavy use of that var not only in avcodec, but also in avformat (and a mention in avdevice) the library versions should have been bump, but upstream failed to do it. I can't be 100% all of this comes from there (as I didn't test), but I strongly suspect that it does in most of these cases.
seems to be fixed in 2.4+; ffmpeg 2.3 has been dropped a while ago
