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 504044 - crash in Epiphany Web Browser:
crash in Epiphany Web Browser:
Status: RESOLVED DUPLICATE of bug 353503
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.20.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-17 13:52 UTC by aaabbbccc
Modified: 2007-12-17 15:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description aaabbbccc 2007-12-17 13:52:10 UTC
Version: 2.20.2

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.21-2-amd64 #1 SMP Tue Jul 10 21:39:38 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 560693248 vsize: 560693248 resident: 88637440 share: 29790208 rss: 88637440 rss_rlim: 18446744073709551615
CPU usage: start_time: 1197889440 rtime: 2412 utime: 2296 stime: 116 cutime:37 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b6f0b9e7e90 (LWP 28544)]
[New Thread 0x44808950 (LWP 28609)]
[New Thread 0x44007950 (LWP 28608)]
[New Thread 0x41001950 (LWP 28546)]
[New Thread 0x40800950 (LWP 28545)]
(no debugging symbols found)
0x00002b6f05d3134f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b6f0b9e7e90 (LWP 28544))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/libgtkembedmoz.so.0d
  • #5 <signal handler called>
  • #6 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_style_attach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 ??
    from /usr/lib/libxul.so.0d
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_rc_reparse_all_for_settings
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_object_notify
    from /usr/lib/libgobject-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #25 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #26 ??
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #28 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 main
  • #0 waitpid
    from /lib/libpthread.so.0

Comment 1 Reinout van Schouwen 2007-12-17 15:28:56 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 353503 ***