Bug#831529: Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

Faidon Liambotis paravoid at debian.org
Mon Jul 25 18:26:25 UTC 2016

reopen 831529
reassign 831529 libavcodec57 7:3.1.1-2
forcemerge 831909 831529


On Sun, Jul 24, 2016 at 02:53:57PM +0200, Sebastian Ramacher wrote:
> On 2016-07-24 14:19:36, Sebastian Ramacher wrote:
> > On 2016-07-22 13:27:09, Faidon Liambotis wrote:
> > > On Fri, Jul 22, 2016 at 10:21:05AM +0200, Sebastian Ramacher wrote:
> > > > Unfortunately I am unable to reproduce the issue. Since there are some accounts
> > > > of random crashes when building ffmpeg with tree vectorization enabled, I've
> > > > uploaded 7:3.1.1-3 with vectorization disabled. Could you please check if the
> > > > issue disappears with -3?
> > > 
> > > I upgraded all ffmpeg packages to 7:3.1.1-3 but I'm still experiencing
> > > crashes.

I followed what the reporter of #831529 suggested: I first tried to "apt
install --reinstall gstreamer1.0-libav", which had no effect. I then
upgraded to the version from experimental, ran gst-launch again, then
downgraded to the version from unstable, which also seem to not crash

I'm not very familiar with the gstreamer/libav/libva stack and thus
would like some help to get to the bottom of this. Frankly, I still
don't understand why x264 and VA-API is even at play here, when it's
just a pipeline of parsing a wav into a fakesink.

Regardless, I'm keeping this as an ffmpeg bug though (and at grave), as
the crashes started with the recent ffmpeg upgrade and the backtraces
seem to suggest that the abort() is coming from ffmpeg.


More information about the pkg-gstreamer-maintainers mailing list