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 637231 - Library Watcher extension consumes RAM until computer becomes unusable
Library Watcher extension consumes RAM until computer becomes unusable
Status: RESOLVED DUPLICATE of bug 617687
Product: banshee
Classification: Other
Component: Metadata
1.8.0
Other Linux
: Normal major
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-12-14 15:05 UTC by Brett Alton
Modified: 2010-12-15 14:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Banshee CPU and RAM usage at 5 second intervals (3.38 KB, text/plain)
2010-12-14 15:06 UTC, Brett Alton
Details
The script I used to produce the log (176 bytes, text/plain)
2010-12-14 15:08 UTC, Brett Alton
Details

Description Brett Alton 2010-12-14 15:05:48 UTC
When Banshee is busy "Saving Metadata to File" under active tasks, it chomps and chomps away at my 4GB of RAM until it uses swap and then my laptop beings to become pretty much unresponsive.

This takes about 3 minutes to occur.

In Edit > Preferences > General, under File Policies, if I disable the last three options "Write metadata to files", "Write ratings and play counts to files" and "Update file and folder names", then Banshee becomes usable and doesn't eat my RAM.

I will be attaching a script I used to record Banshee's RAM/CPU usage as well as the log it produced. Each line in the log is a 5 second interval.
Comment 1 Brett Alton 2010-12-14 15:06:26 UTC
Created attachment 176407 [details]
Banshee CPU and RAM usage at 5 second intervals
Comment 2 Brett Alton 2010-12-14 15:08:44 UTC
Created attachment 176408 [details]
The script I used to produce the log
Comment 3 Gabriel Burt 2010-12-14 18:16:43 UTC
I bet this is a problem actually w/ the LibraryWatcher -- do you have it enabled?  The write-metadata-to-file is just the cause, but (unless I'm wrong) the bug is in LibraryWatcher.

What is the output of running "gconftool-2 --get /apps/banshee-1/sources/_music_library_source_-_library/library-location" in a terminal?
Comment 4 Brett Alton 2010-12-14 22:36:41 UTC
That's very possible because after futher tests, turning off those options does not stop Banshee from eating my RAM.

$ gconftool-2 --get /apps/banshee-1/sources/_music_library_source_-_library/library-location
/media/external/Music

Any other tests I can do? I'm a CS undergrad so you don't have to be easy on me.
Comment 5 Brett Alton 2010-12-15 14:40:29 UTC
Upon further tests, you appear to be correct, this is the 'Library Watcher' extension. When it's disabled, RAM usage stays constant. When enabled, RAM usage constantly climbs.

Should this be set a duplicate of another bug if it's a known issue?
Comment 6 Brett Alton 2010-12-15 14:44:58 UTC

*** This bug has been marked as a duplicate of bug 617687 ***