> > But...I've noticed that my X server seems to grow without bound while I'm
>
> If its the X server, then its an X server bug. X clients have no
> imediate or direct effect on memory management inside the x server.
> The idea is security: no single x client, no matter how malicious,
> is supposed to be able to crash or otherwise mess up the x server.
Unfortunately, I have to disagree with that line of reasoning. A trivial
program doing something like:
while (1)
XCreatePixmap (...);
will cause the X server to grow without bound. There are no per-client
resource limits in the X server.
> When a client goes away, that memory is 'reclaimed'.
In fact, when gnucash exits the server shows signs of having reclaimed all
the memory. Its virtual size, however remains the same - there are almost
no malloc/free implementations that actually return memory to the system.
All the above notwithstanding, an X server or Xlib bug is a possibility
here. However, most of those sorts of bugs got shaken out of X ten years
or more ago. A problem in gnucash (or in the GTK libraries) seems much
more likely to me.
jon
Jonathan Corbet
Executive editor, LWN.net
[EMAIL PROTECTED]
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
