[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KDE4 is a memory hog
From:       Lubos Lunak <l.lunak () suse ! cz>
Date:       2009-07-23 14:50:53
Message-ID: 200907231650.53136.l.lunak () suse ! cz
[Download RAW message or body]

On Tuesday 14 of July 2009, Thiago Macieira wrote:
> Second, I think that the most memory used by X and by kwin is due to pixmap
> caching. Then remember Qt applications do double-buffering too, which leads
> to triple buffering of everything. There was even a bug in Oxygen that
> caused KWin to enable double-buffering of its own, which would lead to
> quadruple-buffering, but I think that has been fixed for a year.

 That wasn't really a bug. Blending doesn't work without the backing pixmap. 
What happened was rather that Oxygen people worked around the blending 
somehow manually, and this should be rather handled properly. Could it be 
e.g. done in Qt that disabling the backing pixmap using Qt::WA_PaintOnScreen 
would actually get rid of the backing pixmap and not just stop using it? Then 
KWin could enable the backing pixmap only for each paint event and then 
discard the memory again.

 Alternatively, it might make sense to make it possible to avoid the backing 
pixmap altogether in Qt, as it's just additional backing pixmap when 
compositing is enabled, but I guess that would be more difficult.

-- 
Lubos Lunak
KDE developer
--------------------------------------------------------------
SUSE LINUX, s.r.o.   e-mail: l.lunak@suse.cz , l.lunak@kde.org
Lihovarska 1060/12   tel: +420 284 084 672
190 00 Prague 9      fax: +420 284 028 951
Czech Republic       http://www.suse.cz
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]