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 606585 - [shout2send] and vorbisenc generates errors
[shout2send] and vorbisenc generates errors
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.16
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-10 22:58 UTC by leon
Modified: 2010-07-15 20:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description leon 2010-01-10 22:58:38 UTC 
When I use playbin2 with vorbisenc + oggmux + shout2send as outputbin it generates the following error:

0:00:35.129861047  5863      0x127efb0 WARN               vorbisenc vorbisenc.c:1197:gst_vorbis_enc_chain:<vorbisenc0> Buffer is older than previous timestamp + duration (0:00:31.843265306< 0:00:31.869387755), cannot handle. Clipping buffer.

Here's someone that has the same problem:
http://www.damonkohler.com/2009/01/rhythmbox-shout2send-plugin.html?showComment=1262193465553#c6109227101281351520

I believe it only occurs when you play the same song after eachother.
When I use the lame encoder it doesn't give any problems. 

It are only warnings but Gstreamer just stops playing and uses 100% cpu.
If I need to clarify anything I would be glad to!
Comment 1 Sebastian Dröge (slomo) 2010-01-14 11:23:04 UTC 
Could you attach with gdb to such a hanging rhythmbox process and look where the threads are spending your CPU on?

Do (with debug packages of libc6, glib, gstreamer, gst-plugins-base installed):

gdb --pid=`pidof rhythmbox`
thread apply all bt
Comment 2 Thiago Sousa Santos 2010-01-15 18:38:48 UTC 
Is this related to https://bugzilla.gnome.org/show_bug.cgi?id=595256 ?
Comment 3 Tobias Mueller 2010-07-15 20:24:01 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!