GNOME Bugzilla – Bug 313832
Segfault when playing mpeg file
Last modified: 2005-10-03 11:41:28 UTC
Opening http://www.eyesopened.nl/~michiel/sacgems/wp-content/movie.mpeg with totem causes a segfault. Backtrace below: GNU gdb 6.3-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/ tls/libthread_db.so.1". (gdb) run Starting program: /opt/gnome/bin/totem [Thread debugging using libthread_db enabled] [New Thread -1227106624 (LWP 16540)] [New Thread -1229669456 (LWP 16743)] [New Thread -1231807568 (LWP 17184)] [New Thread -1241969744 (LWP 17374)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1231807568 (LWP 17184)] 0xb62035b6 in put_pixels_clamped_mmx (block=0x858e080, pixels=0xb5c20a00 "ï¿¿ï¿¿ï¿¿ï¿¿ï¿¿ï¿¿ï¿¿ï¿¿", line_size=576) at dsputil_mmx.c:257 257 __asm __volatile( (gdb) thread apply all bt
+ Trace 62521
Thread 3 (Thread -1231807568 (LWP 17184))
I've tried with current 0.8 cvs and gstreamer doesn't segfault. It displays a weird video but doesn't segfault :) I've tried mplayer and xine and they segfaults. Are you able to play this video with some video player? thanks!
mplayer plays the file just fine over here
ok, i can play it with mplayer -vo x11 but not with xvideo. This pipeline also works: gst-launch-0.8 filesrc location="movie.mpeg" ! decodebin ! ffmpegcolorspace ! ximagesink but this show garbage: gst-launch-0.8 filesrc location="movie.mpeg" ! decodebin ! ffmpegcolorspace ! xvimagesink Can you confirm? Are you using xvideo with mplayer?
It seems to be the same issue as #314897 (if you're not using xvideo with mplayer..)
Marking as duplicate of #314897. Please reopen if mplayer with xvideo works fine. thanks for reporting the bug! *** This bug has been marked as a duplicate of 314897 ***