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 558378 - Crashed when closing epiphany
Crashed when closing epiphany
Status: RESOLVED DUPLICATE of bug 509083
Product: epiphany
Classification: Core
Component: [obsolete] Backend:Mozilla
2.22.x
Other All
: Normal critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-29 11:15 UTC by Sam Morris
Modified: 2008-10-29 13:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sam Morris 2008-10-29 11:15:58 UTC
Steps to reproduce:
This happened when I closed epiphany. The stack trace is not very helpful though.

Stack trace:
Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-amd64 #1 SMP Thu Oct 9 14:16:53 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 487223296 vsize: 487223296 resident: 67887104 share: 29335552 rss: 67887104 rss_rlim: 18446744073709551615
CPU usage: start_time: 1225278109 rtime: 273 utime: 248 stime: 25 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/epiphany-browser'

[Thread debugging using libthread_db enabled]
[New Thread 0x7f39406d0780 (LWP 28016)]
0x00007f39393895ef in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x7f39406d0780 (LWP 28016))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #6 <signal handler called>
  • #7 ??
  • #8 NS_HasPendingEvents_P
    at nsThreadUtils.cpp line 209
  • #9 nsBaseAppShell::OnProcessNextEvent
    at nsBaseAppShell.cpp line 288
  • #10 nsThread::ProcessNextEvent
    at nsThread.cpp line 497
  • #11 NS_ProcessPendingEvents_P
    at nsThreadUtils.cpp line 181
  • #12 nsBaseAppShell::NativeEventCallback
    at nsBaseAppShell.cpp line 121
  • #13 nsAppShell::EventProcessorCallback
    at nsAppShell.cpp line 69
  • #14 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.16.6/glib/gmain.c line 2012
  • #15 g_main_context_iterate
    at /build/buildd/glib2.0-2.16.6/glib/gmain.c line 2645
  • #16 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
  • #17 IA__gtk_main
    at /scratch/build-area/gtk+2.0-2.12.11/gtk/gtkmain.c line 1163
  • #18 main
    at /home/joss/deb/build-area/epiphany-browser-2.22.3/src/ephy-main.c line 753
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (743 sec old) ---------------------
7f3b10793000-7f3b1079d000 r-xp 00000000 fe:00 580950                     /usr/lib/libavahi-gobject.so.0.0.0
7f3b1079d000-7f3b1099d000 ---p 0000a000 fe:00 580950                     /usr/lib/libavahi-gobject.so.0.0.0
7f3b1099d000-7f3b1099e000 rw-p 0000a000 fe:00 580950                     /usr/lib/libavahi-gobject.so.0.0.0
7f3b1099e000-7f3b109ba000 r-xp 00000000 fe:00 445833                     /lib/ld-2.7.so
7f3b109c0000-7f3b109c9000 r--s 00000000 fe:00 393907                     /var/cache/fontconfig/945677eb7aeaf62f1d50efc3fb3ec7d8-x86-64.cache-2
7f3b109c9000-7f3b109cb000 r--s 00000000 fe:00 394005                     /var/cache/fontconfig/99e8ed0e538f840c565b6ed5dad60d56-x86-64.cache-2
7f3b109cb000-7f3b109cf000 r--s 00000000 fe:00 394004                     /var/cache/fontconfig/6eb3985aa4124903f6ff08ba781cd364-x86-64.cache-2
7f3b109cf000-7f3b109d8000 r--s 00000000 fe:00 394003                     /var/cache/fontconfig/6d41288fd70b0be22e8c3a91e032eec0-x86-64.cache-2
7f3b109d8000-7f3b109da000 r--s 00000000 fe:00 393850                     /var/cache/fontconfig/ddd4086aec35a5275babba44bb759c3c-x86-64.cache-2
7f3b109da000-7f3b109db000 r--s 00000000 fe:00 393842                     /var/cache/fontconfig/4794a0821666d79190d59a36cb4f44b5-x86-64.cache-2
7f3b109db000-7f3b109dd000 r--s 00000000 fe:00 393320                     /var/cache/fontconfig/2c5ba8142dffc8bf0377700342b8ca1a-x86-64.cache-2
7f3b109dd000-7f3b109e4000 r--s 00000000 fe:00 393827                     /var/cache/fontconfig/cabbd14511b9e8a55e92af97fb3a0461-x86-64.cache-2
7f3b109e4000-7f3b109f7000 r--s 00000000 fe:00 393832                     /var/cache/fontconfig/e13b20fdb08344e0e664864cc2ede53d-x86-64.cache-2
7f3b10
...Too much output, ignoring rest...
--------------------------------------------------


Other information:
Comment 1 Reinout van Schouwen 2008-10-29 13:17:34 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 509083 ***