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 614963 - 100% cpu when writing to file system during import or metadata change
100% cpu when writing to file system during import or metadata change
Status: RESOLVED INCOMPLETE
Product: banshee
Classification: Other
Component: Metadata
1.6.0
Other Linux
: Normal major
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-06 13:57 UTC by Tanuva
Modified: 2010-09-23 00:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Of course, I should've read the comment about that SIGQUIT... Sorry. Here comes the log. (8.13 KB, text/plain)
2010-04-08 14:47 UTC, Tanuva
Details

Description Tanuva 2010-04-06 13:57:13 UTC
I'm not sure where this error is located. On both media import into the library (dragndrop onto the playback queue) and changes to a file's metadata Banshee's cpu usage raises to 100% and stays there. Both cases imply changing the filesystem as I told Banshee to sync the file and folder names with the actual metadata of the song.
The only warning I can find in ~/.config/banshee-1/log besides moaning about NetworkManager not running is this:

[Warn  15:18:44.089] Forcefully breaking out of RCS loop b/c change in total_width less than 1.0

Doesn't seem directly related to this error because it appears later.
Comment 1 Tanuva 2010-04-06 13:59:48 UTC
And just after committing I remember what I forgot to mention.
100% cpu usage results in Banshee's GUI to be more or less unusable as it freezes every few seconds for a few of those. Music plays fine still (separate thread I guess) but track changes take time, too.
Comment 2 Bertrand Lorentz 2010-04-07 18:15:12 UTC
Could you follow the instructions on the following page to get more information about your problem ?
http://banshee-project.org/contribute/file-bugs/

Please attach the file you get to this bug. It should figure out what Banshee is doing
Comment 3 Tanuva 2010-04-08 14:47:25 UTC
Created attachment 158207 [details]
Of course, I should've read the comment about that SIGQUIT... Sorry. Here comes the log.
Comment 4 Bertrand Lorentz 2010-08-04 14:58:37 UTC
Sorry for the late reply.

It looks like the problem might be in the Library Watcher extension. Could you disable it and see if you still have the high CPU usage ?
Comment 5 Tanuva 2010-08-08 12:19:33 UTC
That's not possible anymore - I noticed that bug on my Sidux installation which got replaced by Ubuntu in the meantime. Here the bug does not occur anymore. Sorry.
Comment 6 Felipe Besoaín Pino 2010-09-23 00:23:04 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!