rhythmbox-metadata process uses 100% cpu, even after closing app

[Ryan Fugger]

Binary package hint: rhythmbox

I store videos and music in the same directory, and have rhythmbox watching that directory for new music. While I am downloading video, the rhythmbox-metadata process uses 100% cpu constantly. Since upgrading to intrepid, that process remains active at 100% cpu even after I close the rhythmbox app. It isn't even set to be a low-priority process (nice = 0).

[Ryan Fugger (rfugger)]

Turns out the rhythmbox app main process was still active after I closed the app, probably related to another bug I just filed (https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/291810) where my Sansa Clip player fails to show up in rhythmbox under intrepid. The rhythmbox process was launched by the system as:

 rhythmbox file:///media/SANSA%20CLIP

Perhaps failing to communicate properly with the device (which worked fine under hardy) caused the app to shutdown improperly.

Also the 100% cpu at nice 0 still isn't cool, especially when there are no new music files for rhythmbox to possibly be indexing (only new video files). And it shouldn't index continually while I'm downloading, just when I'm done.

[Ryan Fugger (rfugger)]

After further investigation, I am unable to replicate the 100% cpu behaviour after closing the app. Possibly the app was just minimized to the notification area and I didn't realize. Sorry.

[Ryan Fugger (rfugger)]

Please note that 100% cpu behaviour still persists while app is running... Just in case that wasn't clear.

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Ryan Fugger (rfugger)]

There is no program crash. This is a problem of using 100% cpu while the program is running. The "even after closing app" part turned out to be invalid, as I wrote above.

[Pedro Villavicencio (pedro)]

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!.

[Ryan Fugger (rfugger)]

Cannot provide a backtrace on program crash because there is no program crash, just inappropriate program behaviour. I will be happy to provide any other information you ask for to help remedy this problem.

[Pedro Villavicencio (pedro)]

Could you attach gdb to that process to see why it's using alot of cpu? it's probably hanged, please read https://wiki.ubuntu.com/Backtrace#Already%20running%20programs

[Ryan Fugger (rfugger)]

It's not hanged -- it still works fine. It is obviously continually trying to index all the constantly-changing video files that I'm downloading.

[Nigel Babu (nigelbabu)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Ryan Fugger (rfugger)]

I know what's causing the bug. It's when I'm downloading many video
files simultaneously into a subdirectory of my rhythmbox library
directory when I have rhythmbox set to "watch my library for new
files". As the downloading files are continually being updated,
rhythmbox continually tries to index them.

My workaround has been to disable rhythmbox's "watch my library for
new files", as I've found that feature terribly buggy for years now.

On Sun, Feb 14, 2010 at 9:01 PM, Nigel Babu <email address hidden> wrote:
> We'd like to figure out what's causing this bug for you, but we haven't
> heard back from you in a while. Could you please provide the requested
> information? Thanks!
>
> --
> rhythmbox-metadata process uses 100% cpu, even after closing app
> https://bugs.launchpad.net/bugs/291813
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Omer Akram (om26er)]

Could we have another confirmation from you rfugger if the issue is happening with rhythmbox in Ubuntu-10.10 so that we could send this bug report to the people writing the software.

[Ryan Fugger (rfugger)]

Rhythmbox-metadata still uses 100% cpu when files are changing
continuously, but it seems to close down fine in 10.10.

Maybe there should be some kind of back-off mechanism? I remember
similar bugs filed with the nautilus thumbnailer some time ago. Not
sure how or even if those were resolved.

[Launchpad Janitor (janitor)]

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]