Bug 1076914 - Slow startup - high cpu
Summary: Slow startup - high cpu
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-16 12:52 UTC by Flóki Pálsson
Modified: 2016-01-18 22:18 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-01-18 22:18:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Flóki Pálsson 2014-03-16 12:52:11 UTC
Description of problem:
Starting up rhythmbox and to see mucic libarary takes much longer time in F21 than F20.  There is also high cpu usage diring this tilm. 

Version-Release number of selected component (if applicable):
rhythmbox-3.0.1-8.fc21.x86_64


How reproducible:
always

Steps to Reproduce:
1.  start rhythmbox
2.  wait for artist, albmun and songs in panel  
3.

Actual results:
Takes much longer time in F21 tnan F20 and high CPU usage.

Expected results:
Similar time as in F20. 

Additional info:
Selecting album resulets in starting in random song.  Not first song in album list.

Comment 1 Matteo Settenvini 2014-04-22 12:24:20 UTC
I can also see this.

At startup, running rhythmbox with strace, I'm swarmed by thousands and thousands of DBus calls to AT-SPI:

sendmsg(4, {msg_name(0)=NULL, msg_iov(2)=[{"l\4\1\1P\0\0\0m\254\2\0w\0\0\0\1\1o\0\36\0\0\0/org/a11y/atspi/accessible/368\0\0\2\1s\0\33\0\0\0org.a11y.atspi.Event.Object\0\0\0\0\0\3\1s\0\17\0\0\0ChildrenChanged\0\10\1g\0\tsiiva{sv}\0\0", 136}, {"\3\0\0\0add\0\367E\1\0\0\0\0\0\4(so)\0\0\0\5\0\0\0:1.55\0\0\0 \0\0\0/org/a11y/atspi/accessible/87389\0\0\0\0\0\0\0\0", 80}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 216

sendmsg(4, {msg_name(0)=NULL, msg_iov(2)=[{"l\4\1\1 \0\0\0n\254\2\0\177\0\0\0\1\1o\0 \0\0\0/org/a11y/atspi/accessible/87390\0\0\0\0\0\0\0\0\2\1s\0\33\0\0\0org.a11y.atspi.Event.Object\0\0\0\0\0\3\1s\0\f\0\0\0StateChanged\0\0\0\0\10\1g\0\tsiiva{sv}\0\0", 144}, {"\7\0\0\0defunct\0\0\0\0\0\0\0\0\0\1i\0\0\0\0\0\0\0\0\0\0", 32}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 176

Also, trying to search for an artist/song triggers a severe slow down, but I cannot tell if the two are related. I think around the GNOME 3.11.90 release Rhythmbox was okay, but I'm just going on my memory. It is definitely a regression, though; we went from almost-instantaneous, to more-than-5-minutes, which is rather annoying.

I have ~20'000 songs in my library, so I can imagine that (if my guess is right) triggering a DBus call multiple times for each song, because the treeview has changed, is rather heavyweight.

Comment 2 Matteo Settenvini 2014-04-23 20:33:35 UTC
FWIW, I can confirm that killing at-spi-bus-launcher makes Rhythmbox responsive again (until it is respawned, that is). 

at-spi on DBus, and updating the treeview, seem to be the culprit of this bug.

Comment 3 Christoph Reiter 2014-05-14 11:02:27 UTC
https://bugzilla.gnome.org/show_bug.cgi?id=730118

Comment 4 Flóki Pálsson 2014-07-03 00:44:23 UTC
ok now.
rhythmbox-3.0.3-2.fc21.x86_64

Comment 5 Flóki Pálsson 2014-09-10 18:23:38 UTC
Now it takes over 30 seconds to list songs.  Ca 17.000.
rhythmbox-3.0.3-4.fc21.x86_64

Comment 6 Flóki Pálsson 2014-11-02 22:08:59 UTC
ok now 
rhythmbox-3.1-1.fc21.x86_64

Comment 7 Jaroslav Reznik 2015-03-03 15:35:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22


Note You need to log in before you can comment on or make changes to this bug.