glib dependency for the X Server

Gabor Gombas gombasg at
Mon Apr 3 05:16:38 PDT 2006

On Mon, Apr 03, 2006 at 07:58:28AM -0400, Owen Taylor wrote:

> So making malloc optionally not abort isn't really an option since it
> would imply changing the signature of almost every function in everal
> library depending on GLib and also changing almost every line of
> code :-). 

For server code, a simple sleep/retry loop can be better than abort
since the server then can resume its operations once the OOM situation
is solved. On the other hand if the OOM is caused by a memory leak in
the server code, then the sleep/retry can make things worse.

Of course a really smart server program can compare the OS-reported
memory usage with it's own estimation and use abort() only if it
suspects a memory leak in its own code...


     MTA SZTAKI Computer and Automation Research Institute
                Hungarian Academy of Sciences

More information about the xorg mailing list