Thank you for the layman's summary. It was a *_very helpful_* summary.
This KDE session loaded 28 hours ago. These are my current stats:
br...@xenophon:~$ ps aux | grep dbus-daemon
102 1201 0.0 0.0 27196 3620 ? Rs Oct14 2:13 dbus-daemon
--system --fork
bruce 8802 2.9 24.6 1294240 1002004 ? Ss Oct15 51:13
/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
bruce 9062 0.0 0.0 7340 884 pts/1 S+ 07:37 0:00 grep
dbus-daemon
root 11149 0.0 0.0 23328 412 ? Ss Oct14 0:00
/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
br...@xenophon:~$ free
total used free shared buffers cached
Mem: 4057808 3612772 445036 0 42420 1067412
-/+ buffers/cache: 2502940 1554868
Swap: 10442196 648436 9793760
br...@xenophon:~$
If I continue to wait, the dbus-daemon RSS memory allocation will
continue to increase. The highest I have ever seen is ~2.6GB or about
66% of memory. By that point, the computer will be close to unusable.
At what point will it be useful for me to generate a massif.out report?
--
dbus-daemon memory leak
https://bugs.launchpad.net/bugs/295741
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
