[apport] totem-video-thumbnailer crashed with SIGSEGV in decode_mb_cavlc()

Bug #99348 reported by Sitsofe Wheeler on 2007-03-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
gstreamer0.10-ffmpeg (Ubuntu)

Bug Description

Binary package hint: totem

Description of the problem:
The gnome thumbnailer crashed while trying to thumbnail a file (https://launchpad.net/ubuntu/+source/totem/+bug/99341 ) which was still downloading. See Bug #99341 for further details.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Mar 31 09:54:58 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/totem-video-thumbnailer
Package: totem-gstreamer 2.18.0-0ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/bin/gnome-video-thumbnailer -s 128 file:///home/sits/Desktop/spolsky.mp4 /tmp/.gnome_thumbnail.C393PT
ProcCwd: /home/sits
Signal: 11
SourcePackage: totem
 decode_mb_cavlc (h=0xb5b8f020) at h264.c:5612
 decode_slice (h=0xde8) at h264.c:7501
 decode_nal_units (h=0xb5b8f020, buf=0x8286058 "",
 decode_frame (avctx=0x8212200, data=0x80ee2e0,
Uname: Linux galvatron 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Sitsofe Wheeler (sitsofe) wrote :
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=424809

Changed in totem:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Changed in gstreamer:
status: Unknown → Unconfirmed

StacktraceTop:?? ()
?? ()
?? ()

Changed in gstreamer:
status: Unconfirmed → Rejected
Changed in gstreamer:
status: Unknown → Confirmed
Changed in gstreamer:
status: Confirmed → Fix Released
Sitsofe Wheeler (sitsofe) wrote :

Sounds like this launchpad bug should be closed fixed...

Changed in gstreamer0.10-ffmpeg (Ubuntu):
status: Confirmed → Fix Released
Changed in gstreamer:
importance: Unknown → Critical
Prosthetic Head (propanone) wrote :

Several bugs I'm on the list for have been retrospectively marked as 'Critical' after being closed as fixed. There may be a good reason for this in each case, but given that several of them had no priority set or were a lower priority and had been left unsolved for quite some time it does look suspiciously like skewing of statistics. ('we've fixed X critical bugs' or 'we fixed 97% of all critical bugs', etc., except that they weren't critical until after they were fixed)

As I said, there may be a very good reason which I've missed or it could be coincidence. I also apologise for posting this here as it may not be the most appropriate place to raise such concerns, but I have no idea of anywhere else more appropriate.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.