GNOME Bugzilla – Bug 680415
Very slow startup with high CPU usage when library folder monitoring/watch is activated
Last modified: 2018-05-24 17:37:43 UTC
Note: this is on version 2.97, but your bugzilla product does not have that version set up. Time to start Rhythmbox (warm start) without library watching: 9 seconds Time to start, with monitoring: more than 5 minutes. Rhythmbox uses 100% CPU during that time, with little visible I/O going on (from the hard drive LED activity) and the UI being unresponsive. Library: nearly 13 000 tracks Hardware: conventional SATA2 hard drive, Core2 Quad CPU Q9300 @ 2.50GHz × 4 Filesystem: ext4 with defaults,noatime Let me know what additional information I can provide. Would a "strace -f -o /tmp/rhythmbox-strace.txt /usr/bin/rhythmbox" help? If so, please provide me with an email address I can send this to.
(In reply to comment #0) > Let me know what additional information I can provide. > Would a "strace -f -o /tmp/rhythmbox-strace.txt /usr/bin/rhythmbox" help? > If so, please provide me with an email address I can send this to. No, sysprof output would probably help.
Created attachment 219449 [details] sysprof output This is quite odd. It might not be due solely to the library folder monitoring. Initially, I thought it was due to a11y being turned on, but I wasn't sure (beyond placebo effect) that killing at-spi2-registryd, at-spi-bus-launcher (and even "gjs-console") made the difference, so I then looked at whether or not library monitoring was turned on... indeed turning it off seemed to work for a couple of shots, but later I would see the slow startup behavior even with monitoring turned off. Or sometimes the reverse would be true (fast startup with monitoring on). I hope these sysprof outputs (both when a slow startup was occuring) might reveal something.
Hi Jonathan, anything odd in those sysprof outputs?
I've been experiencing the same slow performance when the file scan for my android mp3 player is on course, taking a look at the output with --debug flag, seems that Rhythmbox rescans ALL the SD/Internal Memory of the device looking for playlists, it takes about 2 or 3 mins to complete.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/1203.