[Webkit-unassigned] [Bug 147106] [GTK] SIGABRT in WebKitGtk+ 2.8.4 when visiting some pages

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=147106

--- Comment #3 from Michael Catanzaro <mcatanzaro at igalia.com> ---
#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 comment #2)
> 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.

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).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150720/c1c2d6fe/attachment-0001.html>