Summary: | Nepomuk backup eating too much memory when creating backup file | ||
---|---|---|---|
Product: | nepomuk | Reporter: | Jiří Appl <j.appl> |
Component: | general | Assignee: | Vishesh Handa <me> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | domlyons, matija, me, nico.kruber, roman.karlstetter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Jiří Appl
2011-02-05 13:21:27 UTC
I don't know if this is related, but for me nepomuk (or virtuoso-t in the process-list) also uses too much memory, I allowed it to use 200 MB of my RAM, but currently, it uses around 760 MB RAM. I'm using openSUSE 11.4 with KDE SC 4.6.1 and Qt 4.7.2. I'm not know exactly, but I think this didn't happen with KDE SC 4.6.0 I can confirm identical behaviour on my Gentoo using KDE 4.6.2. is it possible, that nepomuk stays with the highest amount of RAM _ever_ set? I observed that behaviour on one of my PCs: I increased it for indexing (why not use more when I'm not there) and decreased it to a normal level afterwards. Recently, I deleted the whole old nepomuk data repository and let it re-index everything (strigi) - et voilà: it now uses the configured amount of 256MB which I did not change during indexing... I have changed distro to ArchLinux, my current KDE SC version is 4.6.3. When I ran the manual backup today, the memory usage was relatively ok, however the temporary backup file grew to approximately 1.3 GB. Then, the memory usage increased considerably. I had to kill it. Overall, I am still unable to perform the manual backup. *** Bug 265737 has been marked as a duplicate of this bug. *** In KDE 4.7.0 it seems to work OK for me now. (In reply to comment #6) > In KDE 4.7.0 it seems to work OK for me now. Minor fixes - I no longer backup akonadi stuff, so there is less stuff to backup, which results in less memory consumption. I need to do a major rewrite, but I need to run it by the other developers before that. Desktop Summit FTW! :D After the Update to 4.7.0 the problem seemed solved. Today there's the next scheduled backup. I'll have an eye on it... Ok, it looks like it is fixed now. Closing the bug. Please feel free to reopen if it is not really fixed, just masked. |