<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] SIGABRT in WebKitGtk+ 2.8.4 when visiting some pages"
href="https://bugs.webkit.org/show_bug.cgi?id=147106#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] SIGABRT in WebKitGtk+ 2.8.4 when visiting some pages"
href="https://bugs.webkit.org/show_bug.cgi?id=147106">bug 147106</a>
from <span class="vcard"><a class="email" href="mailto:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span></b>
<pre>#6 0x00007fc69eef04e2 in std::__throw_bad_function_call() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7 0x00007fc6a7e46b53 in std::function<void (WebCore::PolicyAction)>::operator()(WebCore::PolicyAction) const () from /opt/gnome-os/tanty/epiphany/install/lib/libwebkit2gtk-4.0.so.37
Looks like the std::function was null.
Also, "Thread 637" looks really bad. We shouldn't make more than 20-25 threads.
(In reply to <a href="show_bug.cgi?id=147106#c2">comment #2</a>)
<span class="quote">> I also have a BT from epiphany and a ~600M SIGSEV core from epiphany but I
> suppose that is caused by the SIGABRT in the WebKitGtk+ SIGBART in the UI
> process.</span >
That is probably a separate bug worth reporting: the UI process should not crash during a web process crash (what you reported here is a web process crash).</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>