ram

Bug #834845 reported by Thomas Zahreddin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kupfer
New
Undecided
Unassigned

Bug Description

kupfer 2.0.6 uses up to 1 GB of Ram.

Revision history for this message
David Schneider (dnschneid) wrote :

That's not good. It shouldn't do that.

Could please you provide some more information?
1. What distribution you are using
2. What version of python you have (python --version)
3. What plugins you have enabled
4. How many folders you are monitoring, and approximately how many files are in them
5. How long Kupfer is open before it reaches a gig of ram
6. How you are measuring the memory usage

Thanks for reporting this.

Revision history for this message
Thomas Zahreddin (thomas-zahreddin) wrote :

Hi David,

sorry, for that short description. I was in a hurry and a few days not on the computer with the bug (my desktop).

1.) Ubuntu 11.04 (with all updates)
2.) Python 2.7.1+ (this is the original output,
3.) My language is german, i translate as i suppose the english original is:
Applications, archive manager, selected file, activator (or maybe trip), search internet, file actions, documents, evolution, favorites, bookmarks of Chrome, bookmarks of Epiphany, bookmarks of Firefox, trash, partitions and disks, pidgin, calculator, rhythmbox, shell commands, skype, display text, URL actions, Wikipedia, dictionary and clipboard.
4.) 491262 directories, 2154062 files (yes, ah hell lot of stuff …) - is it possible to restict kupfer only on the first level of folder ?
5.) roughly 4 hours
6.) the gnome systemmonitor shows the memory usage of each process, also for kupfer.py now: 927.9 MB

For test i disabled every plugin and all catalog (4. tab) options -> ~20 MB after start.
With just applications enabled (plugin and catalog) ~21.5 MB after start.
(so i stay with only a few plugins active).

Thanks for your help. If you want more information, feel free to ask.

Revision history for this message
David Schneider (dnschneid) wrote :

Thanks for the info! Kupfer actually doesn't recursively scan directories, precisely for that reason.
Since you offered, here's more questions:

1. How many of those files are in the first level of the directory?
2. Do the files in the directories monitored tend to change frequently, or automatically through other software?
3. Are you still monitoring the directories in the 21.5 MB configuration?
4. Does the memory usage stay low with the 21.5 MB configuration?
5. If so, what plugins did you disable as compared to the leaking configuration?

Hopefully this will narrow down the possible causes.

Revision history for this message
Thomas Zahreddin (thomas-zahreddin) wrote :

1. How many of those files are in the first level of the directory?
306 folders; 518 files (including hiden files and folders)

2. Do the files in the directories monitored tend to change frequently, or automatically through other software?
sure: all .* are config files, which are changed often (eg. last opened files of a application)
others i'm not sure but in the home-directory sit many files, which are automatically safed there.

3. Are you still monitoring the directories in the 21.5 MB configuration?
i have the plugins: Applications, documents and tracker active, in catalog: applications, places and recently opend files

4. Does the memory usage stay low with the 21.5 MB configuration?
no, memory usage grows over time: after 32 hours the memory usage was at 37 MB.

5. If so, what plugins did you disable as compared to the leaking configuration?
archive manager, selected file, activator (or maybe trip), search internet, file actions, evolution, favorites, bookmarks of Chrome, bookmarks of Epiphany, bookmarks of Firefox, trash, partitions and disks, pidgin, calculator, rhythmbox, shell commands, skype, display text, URL actions, Wikipedia, dictionary and clipboard

Revision history for this message
David Schneider (dnschneid) wrote :

Okay, thanks for all the info. Ulrik, any ideas?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.