| Summary: | [GTK] SIGABRT in WebKitWebProcess WebKitGtk+ 2.8.4 and 2.10.x when visiting some pages on dispatchDecidePolicyForNavigationAction | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Andres Gomez Garcia <agomez> | ||||||||||
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> | ||||||||||
| Status: | NEW --- | ||||||||||||
| Severity: | Normal | CC: | agomez, bugs-noreply, cgarcia, mcatanzaro | ||||||||||
| Priority: | P2 | ||||||||||||
| Version: | 528+ (Nightly build) | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=147111 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Andres Gomez Garcia
2015-07-20 05:03:00 PDT
Created attachment 257088 [details]
BT from gdb
I also have a 1.2G core, if needed.
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. #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). (In reply to comment #3) ... > 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). Oh, right. Didn't realize the crashing process was <path_to>/libexec/webkit2gtk-4.0/WebKitWebProcess . Check bug 147111. Created attachment 264385 [details] Another similar BT from gdb This happen when using WebKitGtk+ with my own JHBuild setting: https://github.com/tanty/jhbuild-epiphany/tree/wkgtk-devel Epiphany 3.18.0 and WebKit 2.10.0 I'm running Epiphany with the dconf key: "process-model" = "shared-secondary-process" The compilation was done with CMake args: "-DPORT=GTK -DCMAKE_BUILD_TYPE=Debug -DDEVELOPER_MODE=ON -DCMAKE_C_FLAGS_DEBUG=-g1 -DCMAKE_CXX_FLAGS_DEBUG=-g1" WebKitWebProcess crashed as described on bug 150670. Epiphany didn't crash and re-spawned another WebProcess. This second WebProcess crashed again in this way. This bug is not reproducible in a predictable way. Created attachment 264392 [details]
Yet another similar BT from gdb
This one was obtained just running MiniBrowser.
Happens also in 2.10.3 Created attachment 267688 [details]
And yet another similar BT from gdb
BT obtained from 2.10.4 with CMake args:
'-DPORT=GTK -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS_RELEASE="-O0 -g1 -DNDEBUG -DG_DISABLE_CAST_CHECKS" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g1 -DNDEBUG -DG_DISABLE_CAST_CHECKS"'
|