[sugar] composite memory usage [was Re: frame auto-visibility configuration]
Wed Sep 24 15:43:41 EDT 2008
On Wed, Sep 24, 2008 at 9:31 PM, Erik Garrison <erik at laptop.org> wrote:
> On Thu, Sep 25, 2008 at 12:43:02AM +0530, Sayamindu Dasgupta wrote:
>> FWIW, sometime back, I did some benchmarks with a composite enabled
>> Metacity - results at
>> http://www.mail-archive.com/sugar at lists.laptop.org/msg03613.html
>> Jim had suggested some memory saving tricks at
>> http://www.mail-archive.com/sugar at lists.laptop.org/msg03647.html
> I'm going to try out Jim's suggestion:
> On Thu, 05 Jun 2008 08:38:59 -0700, Jim Gettys wrote:
>> For composition to not eat memory (a full frame buffer's
>> worth/activity), the buried windows need to be "unmapped" in X parlance.
>> When a window is unmapped, X can free the contents of the window even
>> when composite is running (IIRC).
> We have gtk.Window.unmap() to play with.
> The difficult question is how to signal the activities to unmap
> themselves. I suppose we could follow the pattern currently used to
> trigger auto-saves.
I think that if you iconify a window, it will be unmapped by the window manager.
I believe (not sure though) that wnck.Window.minimize() will iconify
it, that can be called from the shell.
More information about the Sugar-devel