<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Threaded Compositor] Flickering when zooming in/out in maps.google.com"
href="https://bugs.webkit.org/show_bug.cgi?id=154069#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Threaded Compositor] Flickering when zooming in/out in maps.google.com"
href="https://bugs.webkit.org/show_bug.cgi?id=154069">bug 154069</a>
from <span class="vcard"><a class="email" href="mailto:cgarcia@igalia.com" title="Carlos Garcia Campos <cgarcia@igalia.com>"> <span class="fn">Carlos Garcia Campos</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=154069#c4">comment #4</a>)
<span class="quote">> The problem here is that the webgl frames are rendered faster than they are
> composited.
> As we only have 2 buffers in GraphicsContext3D to hold the rendered frames,
> sometimes a buffer is reused for rendering when it hasn't been composited
> yet (or while it's being composited), and this causes the flickering.
>
> I'll attach a patch that fixes this by using one extra buffer to hold the
> renderings. This removes the flicker issues.
>
> But at some point we should add a general solution (also for the acc canvas)
> that somehow blocks the renderings when there are no buffers available.</span >
If at some point this is the only blocker to enable the threaded compositor, I prefer to land this to fix the issue. We can always improve it later.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>