<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] WebkitWebProcess crashes on exit on nvidia if threaded compositing is enabled"
href="https://bugs.webkit.org/show_bug.cgi?id=165522#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] WebkitWebProcess crashes on exit on nvidia if threaded compositing is enabled"
href="https://bugs.webkit.org/show_bug.cgi?id=165522">bug 165522</a>
from <span class="vcard"><a class="email" href="mailto:magomez@igalia.com" title="Miguel Gomez <magomez@igalia.com>"> <span class="fn">Miguel Gomez</span></a>
</span></b>
<pre>This problem was introduced by r295734 in the 2.14 branch, where an exit handler was set to release the existent GLContexts. But was fixed in 2.14.3, where that exit handler does not exist anymore.
In trunk and 2.15 branch seems that it already got fixed time ago.
If there were crashes on exit on 2.15 they probably had a different stack trace, as this one is nor reproducible there (there's no exit handler set to release glx contexts).
Actually currently the sharing GLContext doesn't seem to be destroyed at all on exit. I've debugging a bit and only the compositor's GLContext is being destroyed. That should probably be handled in another bug.
Also, I think my previous comment is still valid. We need to make the about-to-be-destroyed context current in order to call glBindFramebuffer on it.</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>