<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - On Wayland, application containing GtkGLArea stops responding if it's not on current workspace"
href="https://bugzilla.gnome.org/show_bug.cgi?id=769835#c14">Comment # 14</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - On Wayland, application containing GtkGLArea stops responding if it's not on current workspace"
href="https://bugzilla.gnome.org/show_bug.cgi?id=769835">bug 769835</a>
from <span class="vcard"><a href="page.cgi?id=describeuser.html&login=carlosg%40gnome.org" title="Carlos Garnacho <carlosg@gnome.org>"> <span class="fn">Carlos Garnacho</span></a>
</span></b>
<pre>(In reply to Jonas Ådahl from <a href="show_bug.cgi?id=769835#c13">comment #13</a>)
<span class="quote">> Review of <span class=""><a href="attachment.cgi?id=342399&action=diff" name="attach_342399" title="wayland: Disable EGL swap interval">attachment 342399</a> <a href="attachment.cgi?id=342399&action=edit" title="wayland: Disable EGL swap interval">[details]</a></span> <a href='review?bug=769835&attachment=342399'>[review]</a> [review]:
>
> Should we maybe check the EGL_MIN_SWAP_INTERVAL and fail up front if we
> cannot configure the EGL context to let us handle the frame scheduling
> ourself?</span >
Yeah, probably makes sense, it seems Mesa eglSwapInterval implementations will
just clamp and return true, so we might still hit this if the context can't
disable frame throttling.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>