Segmentation fault while changing song position by dragging the position bar

Bug #275483 reported by mw
6
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

Linux prime 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 8.04.1
Release: 8.04
Codename: hardy

Architecture: amd64
Version: 0.11.5-0ubuntu8

Rhythmbox crashes while I drag the bar around trying to change position in the song.
Expected: The song skips to a position represented by the progress bar
What Happens instead: First the song stops playing, then the bar becomes unresponsive, then the entire program becomes unresponsive and must be killed.

Attached a backtrace. Hope this helps.

Revision history for this message
mw (mwolffedu) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in rhythmbox:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
mw (mwolffedu) wrote :

Valgrind output.

Revision history for this message
Sebastien Bacher (seb128) wrote :

did you get the issue while getting this log? there is no crash listed there

Revision history for this message
mw (mwolffedu) wrote :

Crap.

Valgrind slowed down the program a lot, as the wiki said it would. After rhythmbox opened I started to play the song and such and it seemed like it had slowed to a stop and crashed, but it may have just been valgrind slowing it down. Sorry, I'll run it again tonight and see if I can get a definitive crash.

Revision history for this message
Sebastien Bacher (seb128) wrote :

valgrind workaround crashes sometimes but you can look in the log for invalid read or write errors

Revision history for this message
mw (mwolffedu) wrote :

OK, here is a new Valgrind, but it doesn't look that much more helpful than the other one. I don't know what I'm doing with Valgrind, though, so maybe there is something in it. I did the same thing that I normally do to reproduce the bug, and the program seemed to hang. I gave it several minutes to make sure it wasn't just Valgrind being slow. Hopefully it shows up in this log.

If I'm not using Valgrind and i just run the program for the console, I can see it actually report a Segmentation Fault sometimes.

Revision history for this message
mw (mwolffedu) wrote :

OK, here is a new Valgrind, but it doesn't look that much more helpful than the other one. I don't know what I'm doing with Valgrind, though, so maybe there is something in it. I did the same thing that I normally do to reproduce the bug, and the program seemed to hang. I gave it several minutes to make sure it wasn't just Valgrind being slow. Hopefully it shows up in this log.

If I'm not using Valgrind and i just run the program for the console, I can see it actually report a Segmentation Fault sometimes.

Revision history for this message
mw (mwolffedu) wrote :

Sorry about the double post.

Additionally, this might be helpful. It is just some of the last lines of output from rhythmbox -d
I also tried the file in VLC and VLC handled it with no problems.

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you use the crossfading option? does not using it workaround the issue?

Revision history for this message
Dan O'Donovan (dodonovan) wrote : Re: [Bug 275483] Re: Segmentation fault while changing song position by dragging the position bar

Yes, actually. I hadn't thought to check that before.
The issue goes away when I turn off cross-fading.

On Wed, 2008-11-05 at 13:28 +0000, Sebastien Bacher wrote:

> do you use the crossfading option? does not using it workaround the
> issue?
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is bug #270700

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.