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 580087 - crash in Epiphany Web Bookmarks: Closing epiphany. Epipha...
crash in Epiphany Web Bookmarks: Closing epiphany. Epipha...
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: 2009-04-24 09:12 UTC by flupi
Modified: 2009-04-24 10:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description flupi 2009-04-24 09:12:21 UTC 
Version: 2.22.3

What were you doing when the application crashed?
Closing epiphany. Epiphany was consuming > 90% of CPU.
Webpage: http://skwpspace.com/git-workflows-book/


Distribution: Debian 5.0.1
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 328097792 vsize: 328097792 resident: 265703424 share: 16068608 rss: 265703424 rss_rlim: 4294967295
CPU usage: start_time: 1240562015 rtime: 98794 utime: 94822 stime: 3972 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 0xb6ac1700 (LWP 3193)]
0xb7f4e424 in __kernel_vsyscall ()

+ Trace 214747

Thread 1 (Thread 0xb6ac1700 (LWP 3193))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #7 <signal handler called>
  • #8 ??
  • #9 NS_HasPendingEvents_P
    at nsThreadUtils.cpp line 194
  • #10 nsBaseAppShell::OnProcessNextEvent
    at nsBaseAppShell.cpp line 288
  • #11 nsThread::ProcessNextEvent
    at nsThread.cpp line 497
  • #12 NS_ProcessPendingEvents_P
    at nsThreadUtils.cpp line 180
  • #13 nsBaseAppShell::NativeEventCallback
    at nsBaseAppShell.cpp line 121
  • #14 nsAppShell::EventProcessorCallback
    at nsAppShell.cpp line 69
  • #15 g_io_unix_dispatch
  • #16 IA__g_main_context_dispatch
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2012
  • #17 g_main_context_iterate
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2645
  • #18 IA__g_main_loop_run
    at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2853
  • #19 IA__gtk_main
    at /tmp/buildd/gtk+2.0-2.12.12/gtk/gtkmain.c line 1163
  • #20 main
    at /build/buildd-epiphany-browser_2.22.3-9-i386-MLTyHU/epiphany-browser-2.22.3/src/ephy-main.c line 753
  • #0 __kernel_vsyscall 


----------- .xsession-errors (396 sec old) ---------------------
** 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)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
(gnome-terminal:2591): Vte-WARNING **: Nessun gestore definito per la sequenza di controllo "device-control-string".
(gnome-terminal:2591): Vte-WARNING **: Nessun gestore definito per la sequenza di controllo "device-control-string".
--------------------------------------------------
Comment 1 Reinout van Schouwen 2009-04-24 10:44:33 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 ***