https://bugzilla.novell.com/show_bug.cgi?id=398401
User R.Vickers@cs.rhul.ac.uk added comment
https://bugzilla.novell.com/show_bug.cgi?id=398401#c9
Bob Vickers changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |R.Vickers@cs.rhul.ac.uk
--- Comment #9 from Bob Vickers 2008-08-15 04:27:32 MDT ---
I am seeing dbus problems as well in the official 11.0 and I think they may
well be the same. The first symptom I saw was dbus crashing with segfault
errors:
zeno kernel: dbus-daemon[1970]: segfault at 1000001f0 ip 7f56642884c5 sp
7fff6d4fd310 error 4 in liblber-2.4.so.2.0.5[7f5664280000+f000]
aspasia kernel: dbus-daemon[23370]: segfault at 1c ip 7fd0409aa040 sp
7fff489c3038 error 6 in dbus-daemon[7fd04097d000+4a000]
Both these machines have a data segment limit of 262144 KB in
/etc/security/limits.conf for non-root processes, so possibly the memory leak
is causing the segfault errors.
I restarted dbus-daemon using valgrind as suggested above, and after an hour or
so I get
$ ps augx | grep `cat /var/run/dbus/pid `
100 10266 0.1 0.1 119916 35520 ? Ss 10:47 0:01
/usr/bin/valgrind --leak-check=full --show-reachable=yes
--log-file=/var/run/dbus/dbus-leak-%p /bin/dbus-daemon --system
I have sent the valgrind output (so far...daemon is still running).
Bob
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.