rhythmbox-metadata crashed with SIGSEGV

[eris23]

Binary package hint: rhythmbox

When starting rhythmbox "rhythmbox-metadata crashed with SIGSEGV" dialog comes up. rhythmbox continues running no apparent problems

ProblemType: Crash
Architecture: amd64
CheckboxSubmission: b97e1ce81faf16ddc9bad6a605ac0c0b
CheckboxSystem: edda5d4f616ca792bf437989cb597002
CrashCounter: 1
Date: Fri Mar 26 15:52:07 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: rhythmbox 0.12.7git20100325-0ubuntu1
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SegvAnalysis:
 Segfault happened at: 0x7f386c711620: movd (%rsi),%mm0
 PC (0x7f386c711620) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%mm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/libavcodec.so.52
 ?? () from /usr/lib/libavcodec.so.52
 ?? () from /usr/lib/libavcodec.so.52
 ?? () from /usr/lib/libavcodec.so.52
 ?? () from /usr/lib/libavcodec.so.52
Title: rhythmbox-metadata crashed with SIGSEGV
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:2382): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:2395): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

[Apport retracing service (apport)]

StacktraceTop:
 avg_h264_chroma_mc4_3dnow (
 hl_decode_mb_complex (h=0x11b3000)
 dsputil_init_mmx (c=0x10ce9e8, avctx=0x7f3800000000)
 ?? ()
 ?? ()

[Pedro Villavicencio (pedro)]

looks like the crash is under libavcodec

[Reinhard Tartler (siretart)]

looks indeed like a null pointer dereference in libavcodec, but unfortunately, the retracer didn't have the proper debug info installed in the chroot, so the retrace is pretty much useless. We now need to verify if rhythmbox is passing garbage to ffmpeg or if there is indeed a problem in the hand written assembler parts of libavcodec.

How can this be reproduced? Can you also reproduce this (somehow) with the ffmpeg or ffprobe commandline tool? does this still happen in trunk?

[Launchpad Janitor (janitor)]

[Expired for ffmpeg (Ubuntu) because there has been no activity for 60 days.]