rhythmbox crashed with SIGSEGV in vorbis_synthesis_blockin()

Bug #146850 reported by yorneb
8
Affects Status Importance Assigned to Milestone
Rhythmbox
New
Undecided
Unassigned
libvorbis (Ubuntu)
In Progress
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

Pressed play on the "Trance radio station" and Rhythmbox crashed.

ProblemType: Crash
Architecture: i386
Date: Sat Sep 29 11:48:42 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.11.2-0ubuntu3
PackageArchitecture: i386
ProcCmdline: rhythmbox
ProcCwd: /home/yorneb
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 vorbis_synthesis_blockin () from /usr/lib/libvorbis.so.0
 ?? () from /usr/lib/gstreamer-0.10/libgstvorbis.so
 ?? ()
 ?? ()
 ?? ()
Title: rhythmbox crashed with SIGSEGV in vorbis_synthesis_blockin()
Uname: Linux senna 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

SegvAnalysis:
 Segfault happened at: 0xb435abf9 <vorbis_synthesis_blockin+585>: fstps 0xfffffffc(%esi,%edx,4)
 PC (0xb435abf9) ok
 source "0xfffffffc(%esi,%edx,4)" (0x09212250) ok
 Stack memory exhausted (SP below stack segment)
 SP (0xb20faa20) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

Revision history for this message
yorneb (yorneb) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:vorbis_synthesis_blockin (v=0x9428088, vb=0x9428120) at ../../lib/block.c:753
vorbis_dec_decode_buffer (vd=0x9428000, buffer=<value optimized out>) at vorbisdec.c:923
vorbis_dec_chain (pad=0x93c2ec8, buffer=0x90ddc68) at vorbisdec.c:1310
gst_pad_chain_unchecked (pad=0x93c2ec8, buffer=0x90ddc68) at gstpad.c:3453
gst_ogg_pad_stream_out (pad=0x8dd2000, npackets=0) at gstoggdemux.c:822

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in rhythmbox:
importance: Undecided → Medium
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. I'm marking this as triaged and forwarding upstream.

Changed in rhythmbox:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in rhythmbox:
status: Unknown → New
Changed in rhythmbox:
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

Upstream thinks that's a libvorbis bug

Changed in rhythmbox:
assignee: desktop-bugs → nobody
status: Triaged → New
Kees Cook (kees)
description: updated
Kees Cook (kees)
description: updated
tags: added: stack-exhaustion
Revision history for this message
Chris Sherlock (ta-bu-shi-da-yu) wrote :

I've looked at the source of the latest libvorbis, and I think you'll find it's changed so much that this may well have been resolved. For instance, the stacktrace shows that vorbis_synthesis_blockin(...) has the variable packet, however there is no such variable anymore in this function.

Revision history for this message
Chris Sherlock (ta-bu-shi-da-yu) wrote :

Oops... sorry, looked at wrong file.

Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. I noticed that the version of Ubuntu your using is in End of Life status. More information may be found at: https://wiki.ubuntu.com/Releases As well, the package version your bugging is updated in Maverick. Please update via www.ubuntu.com repost a detailed error report, and update the bug status. Thanks!

Changed in libvorbis (Ubuntu):
status: New → Incomplete
vlad (vlady-63)
Changed in libvorbis (Ubuntu):
status: Incomplete → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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