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 359103 - Rhythmbox crashes after 3-5 sec. of listening a music... But I'm still listening...
Rhythmbox crashes after 3-5 sec. of listening a music... But I'm still listen...
Status: RESOLVED DUPLICATE of bug 353960
Product: rhythmbox
Classification: Other
Component: general
0.9.6
Other Linux
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-02 20:11 UTC by ididkovsky
Modified: 2006-10-02 21:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description ididkovsky 2006-10-02 20:11:38 UTC
Distribution: Fedora Core release 5 (Bordeaux)
Package: rhythmbox
Severity: Normal
Version: GNOME2.14.3 0.9.6
Gnome-Distributor: Red Hat, Inc
Synopsis: Rhythmbox crashes after 3-5 sec. of listening a music... But
I'm still listening... Bugzilla-Product: rhythmbox
Bugzilla-Component: general
Bugzilla-Version: 0.9.6
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:

Rhythmbox crashes after 3-5 sec. of listening a music... But I'm still
listening...
on 'top' rhythmbox-metad eats 40-50% of cpu at any time.

Steps to reproduce the crash:
1. ./configure --enable-track-transfer --enable-audioscrobbler
--enable-libnotify
2. plugins is on: Lastfm, Lyrics, Art Display
3. start listenig collection (~1400 songs)

Expected Results:

Rhythmbox is halted

How often does this happen?

Every time on 0.9.6 (0.9.5 works fine)

Additional Information:

Buld on updated stable FC5 (Celeron'2000, 512Mb)





Debugging Information:

Backtrace was generated from '/usr/local/bin/rhythmbox'

Using host libthread_db library "/lib/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1208968704 (LWP 25912)]
[New Thread -1288340576 (LWP 26005)]
[New Thread -1298830432 (LWP 26003)]
[New Thread -1309320288 (LWP 26002)]
[New Thread -1267360864 (LWP 25999)]
[New Thread -1256871008 (LWP 25920)]
[New Thread -1241220192 (LWP 25916)]
0x4740d402 in __kernel_vsyscall ()

Thread 1 (Thread -1208968704 (LWP 25912))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 rhythmdb_entry_get_string
    at rhythmdb.c line 3989
  • #11 rb_audioscrobbler_song_changed_cb
    at rb-audioscrobbler.c line 1011

Comment 1 Elijah Newren 2006-10-02 20:19:25 UTC
Looks like the stack trace in bug 347665, but that was supposed to be a stack trace of a bug that was introduced during the development cycle AFAICT.  So, I'll leave this one open for a maintainer to look at.
Comment 2 Jonathan Matthew 2006-10-02 20:53:37 UTC
This indicates you have old plugin binaries in /usr/local/lib/rhythmbox/plugins/ that you need to remove before installing 0.9.6.

rhythmbox-metadata is using CPU time because rb 0.9.6 needs to re-read all your metadata as we added a few previously unsupported fields.

*** This bug has been marked as a duplicate of 353960 ***
Comment 3 ididkovsky 2006-10-02 21:25:05 UTC
Hm... Why you don't remove old installed plugins on "make install" ???? Now works fine, thanks :))))))