totem-gstreamer-video-thumbnailer crashed with SIGSEGV in g_array_append_vals()

[Michael Rooney]

Binary package hint: totem

Crashed while generating a thumbnail in nautilus. I can duplicate it by running the "ProcCmdline" below in a terminal, which results in a segfault.

Jaunty: totem-gstreamer: 2.25.91-0ubuntu3

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/totem-gstreamer-video-thumbnailer
NonfreeKernelModules: nvidia
Package: totem-gstreamer 2.25.91-0ubuntu3
ProcCmdline: /usr/bin/gnome-video-thumbnailer -s 128 file:///media/disk/torrents/24.S07E10.720p.HDTV.X264-DIMENSION.mkv /tmp/.gnome_desktop_thumbnail.S1NOQU
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /usr/lib/libglib-2.0.so.0
 g_array_append_vals () from /usr/lib/libglib-2.0.so.0
 gst_structure_copy () from /usr/lib/libgstreamer-0.10.so.0
 gst_caps_subtract () from /usr/lib/libgstreamer-0.10.so.0
 gst_caps_is_subset () from /usr/lib/libgstreamer-0.10.so.0
Title: totem-gstreamer-video-thumbnailer crashed with SIGSEGV in g_array_append_vals()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:g_array_maybe_expand (array=0x80808080, len=1)
IA__g_array_append_vals (farray=0x80808080,
gst_structure_copy (structure=0x972e530)
gst_caps_subtract (minuend=0x9727d20, subtrahend=0x96dfac0)
gst_caps_is_subset (subset=0x9727d20, superset=0x96dfac0)

[Sebastien Bacher (seb128)]

thank you for your bug report, could you add the video to the bug?

[Michael Rooney (mrooney)]

Here is a file that I can reproduce the error with (it is the first meg of the video obtained using split) by running: "gnome-video-thumbnailer -s 128 xaa out". The result is a segfault.

[Sebastien Bacher (seb128)]

the example is not crashing there, could you open the bug on bugzilla.gnome.org directly too?

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.