lp:~vanvugt/compiz/XDamageReport2

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:compiz/0.9.8 at revision 3265

Sam Spilsbury: Approve on 2012-06-29

Compiz Maintainers: Pending requested 2012-06-28

Diff: 132 lines (+29/-6)

7 files modified

plugins/annotate/src/annotate.cpp (+1/-1)
plugins/composite/src/privates.h (+4/-0)
plugins/composite/src/screen.cpp (+19/-0)
plugins/composite/src/window.cpp (+1/-1)
plugins/copytex/src/copytex.cpp (+1/-1)
plugins/decor/src/decor.cpp (+2/-2)
plugins/opengl/src/texture.cpp (+1/-1)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1007299: Compiz frame rate decreases if application frame rates are too high (unthrottled)

High

Fix Released

Link a bug report

Related blueprints

3249. By Daniel van Vugt on 2012-06-24

Eliminate remaining occurrances of XDamageReportRawRectangles.

3248. By Daniel van Vugt on 2012-06-24

Remember to XSync so what we think are the outstanding damages matches up
with what the server thinks.

3247. By Daniel van Vugt on 2012-06-24

Re-introduce the critical XDamageReport* changes, which seem to have been
clobberd by mergeing lp:compiz.

3246. By Daniel van Vugt on 2012-06-24

Rebase on latest upstream lp:compiz

3245. By Daniel van Vugt on 2012-06-05

Avoid a potential race condition.

If any unhandled damage events that grow the bounding box remain in the queue
when we're rendering a frame, they will count as new damage we don't yet
know about (and so haven't redrawn). However calling XDamageSubtract with
repair==None tells the server we have repaired all damage when it's possible
we haven't repaired the full region described by those unhandled events.

The solution to this is to keep a copy of the bounding box of each damaged
drawable and only tell the server we've repaired the region that we actually
do know about and have repaired.

3244. By Daniel van Vugt on 2012-06-05

Remove the option to configure the damage reporting mode.

3243. By Daniel van Vugt on 2012-06-01

Actually, default to Bounding Box. It gives me lower CPU and fixes a scrolling
artefact that seems to be specific to xchat + Delta Rectangles.

3242. By Daniel van Vugt on 2012-06-01

Remove debug code and shrink the diff.

3241. By Daniel van Vugt on 2012-06-01

Change default damage report mode to Delta Rectangles. While it seems to
perform at least as fast as Bounding Box, and both much faster than
Raw Rectangles, Delta Rectangles should be fastest in more cases I think.

3240. By Daniel van Vugt on 2012-05-31

Record and remove damage in more correct locations.