<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] Crashes and deadlocks in single web process mode"
href="https://bugs.webkit.org/show_bug.cgi?id=160160#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Threaded Compositor] Crashes and deadlocks in single web process mode"
href="https://bugs.webkit.org/show_bug.cgi?id=160160">bug 160160</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=160160#c5">comment #5</a>)
<span class="quote">> Any additional information on why this is occurring in the first place? </span >
I don't think we can use X and most of the graphics drivers from different processes.
<span class="quote">> I don't think CompositingRunLoop should be removed, instead it should be
> made a singleton for now, and later it could be turned into a thread pool.</span >
That's what my previous patch did, converted it into a singleton, but after moving the performSync to the threaded compositor the class became just a wrapper around RunLoop in a separate thread which is what WorkQueue does in the end.</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>