GNOME Bugzilla – Bug 362858
totem crashed on closing (xvimagesink)
Last modified: 2007-08-22 15:59:19 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/totem/+bug/66541 "Played an mp4 movie file a few times in quick succession, closed Totem and the bug report tool came up. http://librarian.launchpad.net/4873808/_usr_bin_totem.1000.crash stacktrace ... " Debug informations got from the crash report: "1093 req->shmseg = shminfo->shmseg; (gdb) thread 1 [Switching to thread 1 (process 22308)]#0 0xb605aec4 in XvShmPutImage (dpy=0x81131f0, port=73, d=71303493, gc=0x85d3138, image=0x8112aa8, src_x=0, src_y=0, src_w=4294967295, src_h=4294967295, dest_x=0, dest_y=0, dest_w=382, dest_h=313, send_event=0) at ../../src/Xv.c:1093 1093 req->shmseg = shminfo->shmseg; (gdb) bt
+ Trace 76790
$1 = (XvImage *) 0x8112aa8 (gdb) p image.obdata $2 = 0x0" libXv doesn't like the obdata being null, is that a libxv issue or should gst make sure it's not null before calling it?
Other ubuntu bug with a similar backtrace: https://launchpad.net/distros/ubuntu/+source/gstreamer0.10/+bug/69213 "totem crashes on dragging mp3 files onto audio visualizer 11 mp3s were dragged from a local folder (on an ntfs read-only partition) and dropped on totem on the visualizer part of the window. there were 12 other local mp3's in the playlist already."
Is this still reproducable with feisty (ie. -base 0.10.12)? IIRC quite a bit of extra locking has been added in various places in xvimagesink.
*** Bug 422616 has been marked as a duplicate of this bug. ***
*** Bug 420245 has been marked as a duplicate of this bug. ***
*** Bug 413148 has been marked as a duplicate of this bug. ***
I closed the Ubuntu bug - we got no reply on that question.
I'm closing it for now as soon as we get more info on the Ubuntu bug we'll re open it, thanks.