GNOME Bugzilla – Bug 723725
Crash with multi-process enable
Last modified: 2014-02-09 23:42:10 UTC
$ gsettings get org.gnome.Epiphany process-model 'one-secondary-process-per-web-view' I think it crash because the popup window it didn't work (as Carlos Garcia Campos say earlier). (epiphany:31991): GLib-GObject-WARNING **: invalid unclassed pointer in cast to 'WebKitWebView' ** (epiphany:31991): CRITICAL **: guint64 webkit_web_view_get_page_id(WebKitWebView*): assertion 'WEBKIT_IS_WEB_VIEW(webView)' failed [Thread 0x7fff5770d700 (LWP 32199) exited] [New Thread 0x7fff56f0c700 (LWP 32228)] [New Thread 0x7fff5670b700 (LWP 32267)] [Thread 0x7fff5670b700 (LWP 32267) exited] [Thread 0x7fffd8c5b700 (LWP 32006) exited] [Thread 0x7fff56f0c700 (LWP 32228) exited] [New Thread 0x7fff56f0c700 (LWP 32310)] Program received signal SIGSEGV, Segmentation fault. g_type_check_instance_cast (type_instance=type_instance@entry=0xeba980, iface_type=9441136) at gtype.c:4002 4002 gtype.c: No such file or directory. (gdb) bt
+ Trace 233132
This has nothing to do with multiprocess. I think that it's because the webview is destroyed and the shell's signal handler is not removed.
Created attachment 268453 [details] [review] EphyWebView: Avoid a dangling signal handler We should use g_signal_connect_object() with the page-created EmbedShell to avoid the callback to be called for the webview after this is destroyed.
Attachment 268453 [details] pushed as bbb6d6a - EphyWebView: Avoid a dangling signal handler
*** Bug 723988 has been marked as a duplicate of this bug. ***