nepomukservicestub memory leak

Bug #571090 reported by Pavel Malyshev on 2010-04-28
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase-runtime (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-runtime

After nearly 2 days of uptime nepomukservicestub uses ~1300M of RAM (RES), while I've suspended file indexing.
$ uptime
 10:27:59 up 1 day, 19:35, 1 user, load average: 2.35, 2.27, 3.01
$ top -n 1
[...]
  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 3366 afunix 20 0 1879m 1.3g 3636 S 0 34.8 1:08.92 /usr/bin/nepomukservicestub nepomukfilewatch

$ dpkg -l | grep kdebase-runtime
iU kdebase-runtime 4:4.4.2-0ubuntu4 runtime components from the official KDE 4 r
iU kdebase-runtime-bin-kde4 4:4.4.2-0ubuntu4 transitional package for kdebase-runtime
ii kdebase-runtime-data 4:4.4.2-0ubuntu4 shared data files for the KDE 4 base runtime
ii kdebase-runtime-data-common 4:4.4.2-0ubuntu4 transitional package for kdebase-runtime-dat

Confirming, with Kubuntu Lucid on x86_64, kdebase-runtime version 4:4.4.2-0ubuntu4.1.

Here's an excerpt from ps showing (among others) a nepomukservicestub nepomukfilewatch process that accumulated a virtual size of 4 GB and resident set size of 1.5 GB. Other nepomuk processes and virtuoso are also quite large:

olo 10819 1.1 3.5 341964 135764 ? S Jun09 15:02 /usr/bin/nepomukservicestub nepomukremovablestorageservice
olo 10789 3.0 3.9 609328 151504 ? Sl Jun09 40:24 /usr/bin/nepomukservicestub nepomukstorage
olo 10820 10.0 4.8 732056 182328 ? SNl Jun09 133:08 /usr/bin/nepomukservicestub nepomukstrigiservice
olo 9992 1.0 4.9 333392 188048 ? Ss Jun09 13:47 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
olo 10795 12.8 6.0 340360 229700 ? Sl Jun09 170:31 /usr/lib/virtuoso/virtuoso-t +foreground +configfile /home/olo/.cache/virtuoso_X10789.ini +wait
olo 10823 0.6 41.3 4128868 1569892 ? Sl Jun09 8:21 /usr/bin/nepomukservicestub nepomukfilewatch

This is a known KDE bug:

https://bugs.kde.org/show_bug.cgi?id=226676 - memory leak in nepomukfilewatch

I think submitting particular document files on which nepomuk leaks memory would help in diagnosing that bug.

BTW, the Nepomuk developer asks for help in locating the memory leak:

http://thread.gmane.org/gmane.comp.kde.devel.core/63824

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

Other bug subscribers

Remote bug watches

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