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 590420 - Epiphany crashed when trying to connect to a URL
Epiphany crashed when trying to connect to a URL
Status: RESOLVED NOTABUG
Product: epiphany
Classification: Core
Component: Backend
2.27.x
Other All
: Normal critical
: ---
Assigned To: Xan Lopez
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-07-31 21:49 UTC by Pacho Ramos
Modified: 2009-07-31 22:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Pacho Ramos 2009-07-31 21:49:36 UTC 
Steps to reproduce:
1.  The problem is that this cannot be reproduced, but I am running epiphany-2.27.5 under gdb always as I usually get crashes like this, I mean, just after starting to connect to a web
2. 
3. 


Stack trace:

+ Trace 216737

  • #0 write
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libglib-2.0.so.0
  • #2 g_io_channel_write_chars
    from /usr/lib/libglib-2.0.so.0
  • #3 soup_socket_write
    from /usr/lib/libsoup-2.4.so.1
  • #4 ??
    from /usr/lib/libsoup-2.4.so.1
  • #5 ??
    from /usr/lib/libsoup-2.4.so.1
  • #6 ??
    from /usr/lib/libsoup-2.4.so.1
  • #7 ??
    from /usr/lib/libsoup-gnome-2.4.so.1
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
    at ephy-main.c line 781 


Other information:
Seems that libsoup is involved, I have libsoup-2.27.5 and webkit-1.1.11

Regards
Comment 1 Dan Winship 2009-07-31 22:13:57 UTC 
This is not a crash. The process gets a SIGPIPE when it tries to write to a socket that the remote server has disconnected, and so gdb stops there. But libsoup handles SIGPIPE correctly, so if you typed "continue", the program would keep going.

You should type "handle SIGPIPE nostop noprint" at the gdb prompt before running the program, and then gdb will ignore the SIGPIPEs too.
Comment 2 Pacho Ramos 2009-07-31 22:34:12 UTC 
Ups, sorry a lot and thanks for the explanation