Breaking the X module ABI in 7.0 ?

[Owen Taylor]

On Mon, 2005-04-11 at 19:29 +0200, Roland Mainz wrote:

> I have another example where this starts to hurt: Memory fragmentation.
> Currently the number one problem for long-running Xservers or Xservers
> running in memory-restricted environments such as Xterminal/Thin clients
> is memory fragmentation. Where does this fragmentation come from ? The
> primary source of this problem are pixmap allocations (well, teaching
> the GTK+ toolkit or Mozilla not to abuse pixmaps for obscure things such
> as double-buffering (ignoring the detail that there are the
> DOUBLE-BUFFER and MultiBuffer extensions) is likely not an option... ;-(

There's no reason why the GTK+ use of pixmaps for double buffering 
(which is the right way to do things, I'd claim) should cause memory
fragmentation ... it allocates *one* pixmap, draws to it and then
frees it. Even the worst possible allocator (and the current scheme
isn't much better than that) should do OK there.

						Owen

(No interest in making every GTK+ program permanently use huge amounts
of memory to maintain persistant back buffers. There are some
interesting things that can be done with Composite, but I don't think
there's much or any applicability of the old buffering extensions to
that.)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.x.org/archives/xorg-arch/attachments/20050411/0ca2f16f/attachment.pgp