Ian Beckwith reported the following on the Debian BTS today. He's using Xserver from the 1.4.1 branch (snapshot from January 31th). His report contains interesting things about dbus being involved in some memory leaks. Let's hope it will help. He says:
After running for 52 days (and adding lots of swap), it was taking up 1831m of virtual memory:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
14893 root 5 -10 1831m 16m 1840 S 0.7 3.6 1690:08 Xorg
I suspect it is something to do with DBus, as running strings(1) on swap produced lots of references to dbus:
$ sudo strings /dev/hda2 /home/sys/swap/* |fgrep org.freedesktop.DBus.Local|wc -l
The strings output contained lots of copies of:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
ECTED EXTERNAL DBUS_COOKIE_SHA1 ANONYMOUS
DBus appears to be working OK (at least running dbus-monitor then starting pidgin produced a flurry of messages).
In case it is relevant, I'm running ion3 with mostly xterms.
The data above was with a recent but non-current version of X from unstable, I've now been running for 19 days with the version that was in unstable 19 days ago, and X is up to 734Mb of VM usage.
I had some strange HAL / DBUS / EVDEV things after some hibernations and resumes of my laptop.
*** Bug 13538 has been marked as a duplicate of this bug. ***
Created attachment 16607 [details]
Hi, seems to me this could be relevant.
I had install the same packages of X server 1.4.1 of my laptop, on laptop of my co-worker which is next to me. And one day after some network problems my laptop and his laptop had a X crash.
I notice that I just had X crash one time a month and in the office.
Last Wednesday I had a X crash.
May 14 18:49:11 segulix NetworkManager: <info> Deactivating device eth0.
May 14 18:49:11 segulix NetworkManager: <info> eth0: canceled DHCP transaction, dhclient pid 30167
May 14 18:49:14 segulix kdm: X server for display :0 terminated unexpectedly
Seems that network problems and Networkmanager can make a X crash !
let's test it:
Fix hal shutdown crash.
Removing the device invalidates its ->next pointer. Copy it aside before
destroying the device.
(cherry picked from commit f52f6c5c7efc281f9ac204fbaa4f71383df7463d)
*** Bug 16574 has been marked as a duplicate of this bug. ***
seems to be fine these days ...