After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 553230 - Skipping in the track with slider will hang the interface (crossfade enabled)
Skipping in the track with slider will hang the interface (crossfade enabled)
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
: 554369 557492 560133 561263 573940 577984 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-09-22 08:31 UTC by Bram Neijt
Modified: 2009-04-05 07:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
debug log with UI disconnect and freezing (412.36 KB, text/plain)
2008-10-04 13:40 UTC, Hew McLachlan
Details

Description Bram Neijt 2008-09-22 08:31:25 UTC
Please describe the problem:
Skipping within a playing track with the cross-fade will hang the user interface, while the music keeps playing. The only way to stop the application is to kill it.

This may be 64bit or Ogg Vorbis VBR problem. Also, this problem is not reproducable with cross-fade disabled. Currently I'm using Ubuntu Itrepid, 64bit, rhythmbox 0.11.6 and GStreamer 0.10.20.

Steps to reproduce:
1. Enable the cross-fade plugin
2. Play a song (I used an Ogg Vorbis VBR song on my 64bit machine)
3. Drag the time slider forward.
4. If this doesn't block the interface, drag the time slider forward again.


Actual results:
The interface will hang, the music keeps playing. The time slider is nolonger updated. The music will not skip to the new position the time-slider points to.

Expected results:
The music to skip and work normally like it does without cross-fade enabled.

Does this happen every time?
Sometimes you need to drag the time-slider twice, but appart from that it can be reproduced.

Other information:
One thing that might help is that, when cross-fade has been disabled and you then drag the slider around, the progress in the time will sometimes show "0.00" just before updating to the right time within the song. It may be that this short indication of "0.00" will trigger the cross-fade plugin to do buffering/loading or other weird things??
Comment 1 Jonathan Matthew 2008-09-30 11:17:43 UTC
*** Bug 554369 has been marked as a duplicate of this bug. ***
Comment 2 Hew McLachlan 2008-10-04 13:40:05 UTC
Created attachment 119915 [details]
debug log with UI disconnect and freezing 

I've experienced this problem too. Sometimes the disconnect occurs between the song and the UI, and sometimes rhythmbox just completely freezes. A bug report for this issue exists at Launchpad: https://launchpad.net/bugs/270700

I have attached my log where I had the UI problem on the first two songs (pressing next worked fine), and on the third song I had rhythmbox freeze.
Comment 3 Jonathan Matthew 2008-10-22 21:14:24 UTC
*** Bug 557492 has been marked as a duplicate of this bug. ***
Comment 4 Jonathan Matthew 2008-10-25 11:04:11 UTC
2008-10-25  Jonathan Matthew  <jonathan@d14n.org>

        * backends/gstreamer/rb-player-gst-xfade.c:
        (adjust_base_time_probe_cb), (adjust_stream_base_time):
        If we can't adjust the stream base time the first time, add a pad
        probe to try again next time a buffer exits the bin.

        (stream_src_event_cb):
        Don't allow flush events to pass outside the stream bin.  Flushing the
        adder or the output bin breaks everything.

        (perform_seek), (unlink_blocked_cb), (stream_src_event_cb),
        (rb_player_gst_xfade_set_time):
        Don't unlink to seek in playing streams.  Not sure where I got the
        idea that this was necessary, but it's completely wrong.

        Fixes #553230.
Comment 5 Jonathan Matthew 2008-11-10 12:33:11 UTC
*** Bug 560133 has been marked as a duplicate of this bug. ***
Comment 6 Jonathan Matthew 2008-11-17 23:31:02 UTC
*** Bug 561263 has been marked as a duplicate of this bug. ***
Comment 7 Jonathan Matthew 2009-03-05 01:32:10 UTC
*** Bug 573940 has been marked as a duplicate of this bug. ***
Comment 8 Jonathan Matthew 2009-04-05 07:52:00 UTC
*** Bug 577984 has been marked as a duplicate of this bug. ***