<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] Loading pages is broken"
href="https://bugs.webkit.org/show_bug.cgi?id=167735#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION(r211486): [GTK] Loading pages is broken"
href="https://bugs.webkit.org/show_bug.cgi?id=167735">bug 167735</a>
from <span class="vcard"><a class="email" href="mailto:joepeck@webkit.org" title="Joseph Pecoraro <joepeck@webkit.org>"> <span class="fn">Joseph Pecoraro</span></a>
</span></b>
<pre>An alternative solution would be to guard the main run loop initialization in Source/JavaScriptCore/runtime/InitializeThreading.cpp with PLATFORM(COCOA) guards. That feels a bit arbitrary, but since I can't test GTK to understand what is happening, and since GTK doesn't currently use the JSContext inspector code, it should be just fine. If I don't hear back by the end of the day I'll speculatively land this change.
To start investigation a backtrace of all threads to see what is happening when RunLoop::initializeMainRunLoop is getting called on GTK would be important.</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>