After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 723725 - Crash with multi-process enable
Crash with multi-process enable
Status: RESOLVED FIXED
Product: epiphany
Classification: Core
Component: General
3.11.x
Other Linux
: Normal critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
: 723988 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-02-05 22:11 UTC by Yosef Or Boczko
Modified: 2014-02-09 23:42 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
EphyWebView: Avoid a dangling signal handler (1.12 KB, patch)
2014-02-07 21:27 UTC, Claudio Saavedra 		committed Details | Review

Description Yosef Or Boczko 2014-02-05 22:11:19 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

  • #0 g_type_check_instance_cast
    at gtype.c line 4002
  • #1 page_created_cb
    at ephy-web-view.c line 667
  • #2 ffi_call_unix64
    from /usr/lib/libffi.so.6
  • #3 ffi_call
    from /usr/lib/libffi.so.6
  • #4 g_cclosure_marshal_generic
    at gclosure.c line 1447
  • #5 g_closure_invoke
    at gclosure.c line 770
  • #6 signal_emit_unlocked_R
    at gsignal.c line 3551
  • #7 g_signal_emit_valist
    at gsignal.c line 3307
  • #8 g_signal_emit
    at gsignal.c line 3363
  • #9 web_extension_page_created
    at ephy-embed-shell.c line 160
  • #10 emit_signal_instance_in_idle_cb
    at gdbusconnection.c line 3738
  • #11 g_main_dispatch
    at gmain.c line 3065
  • #12 g_main_context_dispatch
    at gmain.c line 3640
  • #13 g_main_context_iterate
    at gmain.c line 3711
  • #14 g_main_context_iteration
    at gmain.c line 3772
  • #15 g_application_run
    at gapplication.c line 1695
  • #16 main
    at ephy-main.c line 488 






Comment 1


Claudio Saavedra





          2014-02-07 21:23:59 UTC
        



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.






Comment 2


Claudio Saavedra





          2014-02-07 21:27:55 UTC
        



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.






Comment 3


Claudio Saavedra





          2014-02-07 21:50:04 UTC
        



Attachment 268453 [details] pushed as bbb6d6a - EphyWebView: Avoid a dangling signal handler






Comment 4


Maciej (Matthew) Piechotka





          2014-02-09 23:42:10 UTC
        



*** Bug 723988 has been marked as a duplicate of this bug. ***