Launchpad has imported 8 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=265737.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2011-02-07T23:18:09+00:00 Domlyons-n wrote:
Version: unspecified (using KDE 4.6.0)
OS:Linux
At the moment a nepumikservices process eats more than 7 GB RAM. This
doesn't happen every day but every few days.
I can't imagine how this can happen as nepomuk is restricted to 256 MB
in systemsettings and soprano-virtuoso.db is "only" about nearly 900 MB.
What is noticeable:
* Internet access was broken for more than half an hour - could that
have a (crazy) impact? I guess it at least should not...
* After connection was there again Akonadi neither reconnected GMail
IMAP nor Kolab disconnected IMAP - but I guess that shouldn't do Nepomuk
any harm
* Today Nepomuk backup was scheduled at 21.00. I didn't recognize if excessive
RAM usage just started that time... But else than Bug 265510 ("Nepomuk backup
eating too much memory when creating backup file") I don't seem to have a big
temp-file.
But all that ps can say it seems to be a problem with the backup (see below)
$ ps -AF | grep nepomuk
dominic 2081 1 0 52815 9432 0 18:41 ?00:00:00
/usr/bin/nepomukserver
dominic 2086 2081 12 190888 139352 3 18:41 ?00:32:43
/usr/bin/nepomukservicestub nepomukstorage
dominic 2103 2017 0 74585 22008 3 18:41 ?00:00:06
/usr/bin/akonadi_nepomuk_calendar_feeder --identifier
akonadi_nepomuk_calendar_feeder
dominic 2104 2017 0 73921 22088 2 18:41 ?00:00:06
/usr/bin/akonadi_nepomuk_contact_feeder --identifier
akonadi_nepomuk_contact_feeder
dominic 2105 2017 0 110529 32516 2 18:41 ?00:00:09
/usr/bin/akonadi_nepomuk_email_feeder --identifier akonadi_nepomuk_email_feeder
dominic 2394 2081 0 91383 21996 0 18:42 ?00:00:09
/usr/bin/nepomukservicestub nepomukqueryservice
dominic 2395 2081 0 109306 26128 3 18:42 ?00:00:23
/usr/bin/nepomukservicestub nepomukfilewatch
dominic 2400 2081 12 1911954 7253580 3 18:42 ? 00:32:17
/usr/bin/nepomukservicestub nepomukbackupsync
dominic 2402 2081 0 123711 32952 5 18:42 ?00:00:08
/usr/bin/nepomukservicestub digikamnepomukservice
dominic 2403 2081 0 141079 51976 5 18:42 ?00:01:38
/usr/bin/nepomukservicestub nepomukstrigiservice
dominic 2404 2081 0 89432 22536 0 18:42 ?00:00:08
/usr/bin/nepomukservicestub nepomukremovablestorageservice
dominic 5296 2145 0 2595 852 1 23:07 pts/000:00:00 grep
--color=auto nepomuk
And that's what ksysguard says:
Process 2400 - nepomukservices
Summary
--
The process nepomukservices (with pid 2400) is using approximately 6.9 GB of
memory.
It is using 6.9 GB privately, and a further 17.3 MB that is, or could be,
shared with other programs.
Dividing up the shared memory between all the processes sharing that memory we
get a reduced shared memory usage of 346.0 KB. Adding that to the private
usage, we get the above mentioned total memory footprint of 6.9 GB.
4.0 KB is swapped out to disk, probably due to a low amount of available memory
left.
Library Usage
--
The memory usage of a process is found by adding up the memory usage of each of
its libraries, plus the process's own heap, stack and any other mappings, plus
the stack of its 2 threads.
Private
--
7233680 KB [heap]
284 KB /usr/lib/libQtGui.so.4.7.0
204 KB /usr/lib/libkdeui.so.5.6.0
132 KB /usr/lib/libkdecore.so.5.6.0
116 KB /usr/lib/kde4/nepomukbackupsync.so
Shared
--
2648 KB /usr/lib/libQtGui.so.4.7.0
1760 KB /usr/lib/libkdeui.so.5.6.0
1560 KB /usr/lib/libkdecore.so.5.6.0
1396 KB /usr/lib/libQtCore.so.4.7.0
704 KB /usr/lib/libkio.so.5.6.0
Totals
--
Private 7235992 KB (= 188 KB clean + 7235804 KB dirty)
Shared 17724 KB(= 17724 KB clean + 0 KB dirty)
Rss 7253716 KB (= Private + Shared)
Pss 7236338 KB (= Private + Shared/Number of Processes)
Swap4 KB
Reproducible: Sometimes
Steps to Reproduce:
That's a really good question...
Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase-
runtime/+bug/777295/comments/0
On 2011-02-08T00:44:17+00:00 Domlyons-n wrote:
> Steps to Reproduce:
> That's a really good question...
Well, maybe I wrote this a bit too quick...
I've started a manual nepomuk backup. It looked really fine for
