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 539585 - crash in Epiphany Web Browser: closed epiphany
crash in Epiphany Web Browser: closed epiphany
Status: RESOLVED DUPLICATE of bug 509083
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.22.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-22 12:40 UTC by Sam Morris
Modified: 2008-06-22 12:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Sam Morris 2008-06-22 12:40:02 UTC 
Version: 2.22.2

What were you doing when the application crashed?
closed epiphany


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-rc6 #2 SMP Fri Jun 13 11:14:18 BST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 494571520 vsize: 494571520 resident: 61759488 share: 28864512 rss: 61759488 rss_rlim: 18446744073709551615
CPU usage: start_time: 1214138080 rtime: 172 utime: 155 stime: 17 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x7ff1ffd4a780 (LWP 29062)]
0x00007ff1f8633edf in waitpid () from /lib/libpthread.so.0

+ Trace 201075

Thread 1 (Thread 0x7ff1ffd4a780 (LWP 29062))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #5 <signal handler called>
  • #6 ??
  • #7 NS_HasPendingEvents_P
    at nsThreadUtils.cpp line 207
  • #8 nsBaseAppShell::OnProcessNextEvent
    at nsBaseAppShell.cpp line 288
  • #9 nsThread::ProcessNextEvent
    at nsThread.cpp line 497
  • #10 NS_ProcessPendingEvents_P
    at nsThreadUtils.cpp line 180
  • #11 nsBaseAppShell::NativeEventCallback
    at nsBaseAppShell.cpp line 121
  • #12 nsAppShell::EventProcessorCallback
    at nsAppShell.cpp line 69
  • #13 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.16.3/glib/gmain.c line 2009
  • #14 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.3/glib/gmain.c line 2642
  • #15 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.3/glib/gmain.c line 2850
  • #16 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 1163
  • #17 main
    at /scratch/build-area/epiphany-browser-2.22.2/src/ephy-main.c line 744
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (17 sec old) ---------------------
sys:1: Warning: g_hash_table_unref: assertion `hash_table != NULL' failed
sys:1: Warning: value "((GaProtocol) 2)" of type `GaProtocol' is invalid or out of range for property `flags' of type `GaProtocol'
sys:1: Warning: g_hash_table_unref: assertion `hash_table != NULL' failed
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** (epiphany-browser:29062): WARNING **: Unable to delete /home/sam/.gnome2/epiphany/favicon_cache/42e6575efe60622381aedf0304fbd36f
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-22 12:41:35 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 ***