rhythmbox crashes when seeking in <=96kbps mp3 files

Bug #129472 reported by Alec Wright
2
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

When I try to seek in an mp3 of a standard bitrate less than or equal to 96kbps (96, 80, 64, 56, 48, 40, 32) in rhythmbox, it either freezes, crashes and closes immediately, or reports an internal data flow error. However, >96kbps seeks fine (112, 128, 160, 192 etc).

Revision history for this message
Alec Wright (alecjw) wrote :

This affects gutsy btw

Revision history for this message
Alec Wright (alecjw) wrote :

Other info:
I'm legally required to tell you that the song I uploaded is there's nothing impossible, by deus (http://www.jamendo.com/en/album/103/). It's cc by-nc-sa licensed.
Here's the original ogg vorbis: http://mihd.net/c53jxk
Here it is in all standard bitrates between 32k and 192k: http://mihd.net/50slxd

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash 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
Alec Wright (alecjw) wrote :

I think the attached .crash is the relevant backtrace. I have'nt installed rhythmbox-dbgsym, but I don't need it if i can get the .crash anyway do I?

Revision history for this message
Alec Wright (alecjw) wrote :

I've also realised that rhythmbox -d says this when it crashes:
(20:51:31) [0x80fa408] [check-imperfect] rb-player-gst-xfade.c:1523: file:///home/alec/Music/bitratetest/96.mp3: imperfect-timestamp, prev-timestamp=(guint64)1439727891, prev-duration=(guint64)36009070, prev-offset=(guint64)63492, prev-offset-end=(guint64)65080, cur-timestamp=(guint64)2340000000, cur-duration=(guint64)35736961, cur-offset=(guint64)103194, cur-offset-end=(guint64)104770
(20:51:31) [0x80fa408] [check-imperfect] rb-player-gst-xfade.c:1523: file:///home/alec/Music/bitratetest/96.mp3: imperfect-offset, prev-timestamp=(guint64)1439727891, prev-duration=(guint64)36009070, prev-offset=(guint64)63492, prev-offset-end=(guint64)65080, cur-timestamp=(guint64)2340000000, cur-duration=(guint64)35736961, cur-offset=(guint64)103194, cur-offset-end=(guint64)104770
Segmentation fault (core dumped)

And I've also found out that it only happens with xfade backend. With xfade disabled, it works fine.

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

What do you call "xfade backend"? How do you active it?

Revision history for this message
Alec Wright (alecjw) wrote :

I mean crossfade. Go to Preferences in the Edit menu and then go to the Playback tab. Tick the "Enable crossfading effects" checkbox, and move the slider to 0 seconds. Make sure crossfade between songs in the same album is unchecked. (0 second crossfade=gapless playback. That's what I use it for.) Restart rhythmbox and then try and seek in a 96kbit mp3. (Once you've finished this, you'll probably want to disable crossfade again, as it seems to me that there are quite a lot of other problems with it, eg inability ot play m4a/aac).

Revision history for this message
Alec Wright (alecjw) wrote :

Ah I've just realised that backtrace is completely different to the .crash file.... So the backtrace is attached.

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

Could you install gstreamer0.10-plugins-base-dbg libglib2.0-0-dbg rhythmbox-dbg and get a new backtrace?

Revision history for this message
Alec Wright (alecjw) wrote :

Here it is. The only difference from what you asked for is I used rhythmbox-dbgsym rather than rhythmbox-dbg, because aptitude said no candidate version found for -dbg. I hope thats ok :)

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

looks like you didn't type "thread apply all bt" correctly, could you try again?

Revision history for this message
Alec Wright (alecjw) wrote :

Ok the symptoms have changed. It doesn't make it actually crash anymore so I cant get a backtrace.
Usually you can skip once, or perhaps a few times, but then when you try to skip again, either the slider will carry on moving but the song will not play or the slider will not move and the song wont play. It will say in the properties "Internal data flow error"
Often if you start another song playing, then switch back to the song, the same thing will happen again. However, sometimes it will just freeze and make you kill it, but it will never actually crash.

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

the bug is not clear, maybe it should be closed and a new one opened

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Agreed, closing it for now, feel free to open a new one.

Changed in rhythmbox:
status: Incomplete → Invalid
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.