<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [GTK] BadDamage X Window System error in WebKit::AcceleratedBackingStoreX11::update when called from WebPageProxy::exitAcceleratedCompositingMode"
href="https://bugs.webkit.org/show_bug.cgi?id=164303#c18">Comment # 18</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [GTK] BadDamage X Window System error in WebKit::AcceleratedBackingStoreX11::update when called from WebPageProxy::exitAcceleratedCompositingMode"
href="https://bugs.webkit.org/show_bug.cgi?id=164303">bug 164303</a>
from <span class="vcard"><a class="email" href="mailto:agomez@igalia.com" title="Andres Gomez Garcia <agomez@igalia.com>"> <span class="fn">Andres Gomez Garcia</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=164303#c16">comment #16</a>)
...
<span class="quote">> I would say more: I *really* would like that we trap all X error for the
> whole UIProcess and we just print them on stdout instead of crashing.
>
>
> I really hate when things crash. I rather prefer to be on the wrong side by
> protecting things more than needed than be on the wrong side by crashing on
> corner cases that were not detected when this was implemented.</span >
Like with asserts, crash should be left for debug builds. For a release build, this should be avoided, IMHO.</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>