Why does the xorg server consumes so much memory?

Juergen Beisert juergen127 at kreuzholzen.de
Sat Apr 28 05:18:43 PDT 2007


Hi,

when I run the xorg server on my small X terminal some programs (running on a 
different machine, connected to via "-query" option) will consume the whole 
memory on my local terminal. Most of the time OOM kills the xorg, sometimes 
the terminal freezes only.

For example when I start KDE's konqueror on my remote computer with the page 
http://ftp.franken.de/kongress/99/kenner1/index.html this will kill my local 
32Mbyte terminal. It seems the local xorg caches all pictures (or something 
else, I don't know).
I checked it from a different machine (with 512MByte RAM), also connected 
via "-query" option to my remote computer. The remotely running konqueror 
with the webpage above lets the local xorg consume about 55MByte of system 
RAM!
When I close the remote konqueror process the local xorg server frees the most 
of this memory and continuous to allocates 15MByte of system RAM only.

I tried with the xorg "-ld <int>" and "-ls <int>" options, but without a 
success.

Is there a way to limit the memory the xorg server allocates when running? My 
terminals are running with NFS root, so I don't have any swap space.

These extensions are currently enabled (from Xorg.0.log):
[...]
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
[...]

Regards,
Juergen




More information about the xorg mailing list