diff options
author | Adam Jackson <ajax@redhat.com> | 2016-02-02 13:49:37 -0500 |
---|---|---|
committer | Adam Jackson <ajax@redhat.com> | 2016-06-21 11:11:49 -0400 |
commit | 5d6ad0d3a7611c4dff2d79b6af9eb5c0885656ef (patch) | |
tree | 032a43ec4074dc170586d8a46f373e59de249dc8 /glx/glxext.c | |
parent | 4f8a72034c4a2654bfc16d929e09a69d1cc138ef (diff) |
res: Fix accounting of redirected window pixmaps for Composite
The previous change removed the special case that matched resources of
CompositeClientWindowType and walked back from that to the window
pixmap. That was intentional, since that logic was broken anyway. CCWTs
don't map 1:1 to references on the backing pixmap; a window redirected
by multiple clients (say, by the server since it's on the synthetic
visual, and then manually by a compositor) would have a window pixmap
refcount of 1, but would have those bytes accounted twice.
The right thing is to have Composite wrap window accounting, and add the
pixmap bytes once and only once for the redirection reference.
Note that the view from the client can still be non-intuitive in the
face of Composite. xcompmgr, for example, holds _two_ references to
each window pixmap (one each from CompositeNameWindowPixmap and
RenderCreatePicture), so a synthetic-visual window will have its bytes
split 2/3 to xcompmgr and 1/3 to the server-client. Nothing to be done
about that, and at least this way we're not over-accounting.
Acked-by: Michel Dänzer <michel.daenzer@amd.com>
Signed-off-by: Adam Jackson <ajax@redhat.com>
Diffstat (limited to 'glx/glxext.c')
0 files changed, 0 insertions, 0 deletions