<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION(r211486) [GTK] The MiniBrowser doesn't work anymore."
href="https://bugs.webkit.org/show_bug.cgi?id=167776#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION(r211486) [GTK] The MiniBrowser doesn't work anymore."
href="https://bugs.webkit.org/show_bug.cgi?id=167776">bug 167776</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 some places we do:
JSC::initializeThreading();
WTF::initializeMainThread();
in others:
JSC::initializeThreading();
WTF::initializeMainThread();
RunLoop::initializeMainRunLoop();
and in others even:
WTF::initializeMainThread();
JSC::initializeThreading();
In iOS the web thread does this:
// WTF::initializeMainThread() needs to be called before JSC::initializeThreading() since the
// code invoked by the latter needs to know if it's running on the WebThread. See
// <rdar://problem/8502487>.
WTF::initializeMainThread();
WTF::initializeWebThread();
JSC::initializeThreading();
So, a quick solution to this bug could be doing this in InitializeWebKit2
WTF::initializeThreading();
WTF::initializeMainThread();
JSC::initializeThreading();
But I think we should check all the callers of all initializeThreading methods to make it consistent.</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>