GNOME Bugzilla – Bug 695166
After updating to 1.0.5, while loading a movie file in totem , totem is segmentation fault.
Last modified: 2013-03-09 23:23:28 UTC
After updating to 1.0.5, while loading a movie file , totem is segmentation fault. Program received signal SIGSEGV, Segmentation fault.
+ Trace 231590
Thread 140736079062784 (LWP 2653)
totem-3.6.3-4.fc19.x86_64 gstreamer1-1.0.5-2.fc19.x86_64 gstreamer1-libav-1.0.5-1.fc19.x86_64
Any chance you can provide the movie?It does feel like a libav bug.
(In reply to comment #1) > Any chance you can provide the movie?It does feel like a libav bug. http://file.ruliweb.com/news/2013/02/ps3/ruliweb_mlb13_ps3_sd.wmv ( baseball video game play movie)
or streaming movie mms://yonhapnews.hvod.nefficient.co.kr/yna/201303/MYH20130305002500038_WMV500Kbps.wmv
$wget http://mediadownloads.mlb.com/mlbam/2013/03/01/14-363061-2013-03-01/web_cut/rth_lanana_25643471_1200k.mp4 (baseball play movie) $gdb gst-launch-1.0 (gdb) r -v playbin uri=file:///path/to/rth_lanana_25643471_1200k.mp4 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe7fff700 (LWP 4706)] 0x00007fffe6a8ce49 in dsputil_init (c=c@entry=0x7ffff7f225d8, avctx=0x7fffdc03b8c0) at libavcodec/dsputil.c:3161 3161 c->avg_2tap_qpel_pixels_tab[0][i]= c->avg_h264_qpel_pixels_tab[0][i]; [skip]
All of these work fine for me with the 1.0 git branch and the 1.0.5 packages as in debian. What libav/libffmpeg version is this built against? Is it using the internal libav snapshot or an external libav/libffmpeg?
(In reply to comment #5) > All of these work fine for me with the 1.0 git branch and the 1.0.5 packages as > in debian. > > What libav/libffmpeg version is this built against? Is it using the internal > libav snapshot or an external libav/libffmpeg? libav-0.8.5 http://buildsys.rpmfusion.org/plague-results/fedora-development-rpmfusion_free/gstreamer1-libav/1.0.5-1.fc19/SRPM/ $rpm -qpl gstreamer1-libav-1.0.5-1.fc19.src.rpm gst-ffmpeg-0.10.12-ChangeLog-UTF-8.patch gst-libav-1.0.5.tar.xz gstreamer1-libav.spec libav-0.8.5.tar.xz ~~~~~~~~~~~~~~~~~~
I wonder if this could be a duplicate of bug 694230 ? sangu, can you try running the video in question like this: gst-launch-1.0 filesrc location=rth_lanana_25643471_1200k.mp4 ! qtdemux ! avdec_h264 max-threads=1 ! xvimagesink And also with max-threads=0 and max-threads=2 ?
(gdb) r filesrc location=rth_lanana_25643471_1200k.mp4 ! qtdemux ! avdec_h264 max-threads=1 ! xvimagesink Starting program: /usr/bin/gst-launch-1.0 filesrc location=rth_lanana_25643471_1200k.mp4 ! qtdemux ! avdec_h264 max-threads=1 ! xvimagesink [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Setting pipeline to PAUSED ... [New Thread 0x7fffec56d700 (LWP 6637)] [New Thread 0x7fffebd6c700 (LWP 6638)] Pipeline is PREROLLING ... Program received signal SIGSEGV, Segmentation fault.
+ Trace 231594
Thread 140737150109440 (LWP 6638)
And max-threads=0 and max-threads=2 have the same results.
Hmm, the only non-standard thing about the rpmfusion packages you're using that I've replaced the bundled libav-0.8.4 copy with the libav-0.8.5 tarbal from libav upstream. Note it is still built-in using the standard configure options passed from the gstreamer-libav configure script. Also Tim said in comment $5 that the 1.0 git branch works fine for him, and that branch has been upgraded to libav-0.8.5 too. I've tried to reproduce the crash, but I cannot reproduce it on both my laptop and my desktop, both of which are running F-18 x86_64, I see that you're running rawhide, so perhaps this is a rawhide only issue, possibly in some other component?
This is a libav bug. I've filed a bugreport with a patch attached at https://bugzilla.libav.org/show_bug.cgi?id=469
Ah, I see, only happens with gcc 4.8. Thanks for the update!