https://bugs.kde.org/show_bug.cgi?id=326704

            Bug ID: 326704
           Summary: akonadi_nepomuk_feeder using large amounts of memory
                    after rebuild of Akonadi database
    Classification: Unclassified
           Product: Akonadi
           Version: 4.11
          Platform: Debian unstable
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Nepomuk Feeder Agents
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected]

Due to the CPU contention issue with Akonadi, I had to use this piece of
advice:
https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/909022/comments/7
This worked, and CPU use by Akonadi components is back to a tolerable level.

However, after the Akonadi database rebuild finished, akonadi_nepomuk_feeder is
still holding on to a lage amount of memory, as visible in the attached smaps
file and pmap -x output.

Reproducible: Didn't try

Steps to Reproduce:
1. Get a decently sized mail collection of ~40000 mails with attachments or
more.
2. Be forced to wipe Akonadi database due to unusability.
3. Have Nepomuk indexing enabled, you want to search all that mail.
4. Wait a long time for database rebuild to finish.
Actual Results:  
akonadi_nepomuk_feeder now holds onto a lot of memory, most of it on its heap
(anonymous, non-shared memory).

Expected Results:  
akonadi_nepomuk_feeder should not have to keep all that memory, as the data is
supposedly indexed and stored in virtuoso?

Mail is stored in several seperate akonadi_imap_resource and a few pieces in a
local mail folder.
Reproducing tends to take about a day, which is why it was not done.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Kdepim-bugs mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kdepim-bugs

Reply via email to