[Wayland-bugs] [Bug 761312] memory leak

gtk+ (GNOME Bugzilla) bugzilla at gnome.org
Wed Feb 3 03:19:09 UTC 2016


https://bugzilla.gnome.org/show_bug.cgi?id=761312

--- Comment #39 from Ray Strode [halfline] <rstrode at redhat.com> ---
Created attachment 320308
  --> https://bugzilla.gnome.org/attachment.cgi?id=320308&action=edit
wayland: always return FALSE from begin_paint

The client and compositor share access to the window
pixel buffers. After the client hands off (commits)
the buffer to the compositor it's not supposed to write
to it again until it's released by the compositor.

The code tries to deal with this contention by allocating
a temporary buffer and using that in the mean time. This
temporary buffer is allocated by a higher layer of the code
when begin_paint returns TRUE. Unfortunately, that layer of
the code has no idea when the buffer is released, so it ends
up blitting the temporary buffer back to the shared buffer
prematurely.

This commit changes begin_paint to always return FALSE.

A future commit will address the contention problem in
a different way.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20160203/43d28fd9/attachment.html>


More information about the wayland-bugs mailing list