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 522339 - crash in Epiphany Web Browser: Nothing.. just crashes r...
crash in Epiphany Web Browser: Nothing.. just crashes r...
Status: RESOLVED DUPLICATE of bug 516008
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-03-14 00:26 UTC by Albert Hopkins
Modified: 2008-03-14 10:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Albert Hopkins 2008-03-14 00:26:08 UTC
Version: 2.22.0

What were you doing when the application crashed?
Nothing.. just crashes randomly. Even while viewing about:blank



Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.22.0 2008-03-11 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-gentoo-r3 #1 SMP Sat Mar 1 08:16:49 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Gion

Memory status: size: 148066304 vsize: 148066304 resident: 40693760 share: 26484736 rss: 40693760 rss_rlim: 4294967295
CPU usage: start_time: 1205454241 rtime: 125 utime: 115 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034hReally redefine built-in command "frame"? (y or n) [answered Y; input not from terminal]
Really redefine built-in command "thread"? (y or n) [answered Y; input not from terminal]
Really redefine built-in command "start"? (y or n) [answered Y; input not from terminal]
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb5daa8e0 (LWP 24867)]
[New Thread 0xb0d40b90 (LWP 24877)]
[New Thread 0xb1541b90 (LWP 24876)]
[New Thread 0xb24a1b90 (LWP 24875)]
[New Thread 0xb2ca2b90 (LWP 24874)]
[New Thread 0xb34c1b90 (LWP 24873)]
[New Thread 0xb3d21b90 (LWP 24869)]
[New Thread 0xb5a72b90 (LWP 24868)]
_______________________________________________________________________________
     eax:FFFFFE00 ebx:0000613E  ecx:0819401C  edx:00000000     eflags:00200293
     esi:0819401C edi:FFFFFFFF  esp:08193F34  ebp:08194038     eip:B7F13410
     cs:0073  ds:007B  es:007B  fs:0000  gs:0033  ss:007B    o d I t S z A p C 
[007B:08193F34]---------------------------------------------------------[stack]
08193F64 : 00 00 00 00  00 00 00 00 - 00 00 00 00  00 00 00 00 ................
08193F54 : 1C 40 19 08  00 00 00 00 - 00 00 00 00  00 00 00 00 .@..............
08193F44 : F4 0F CF B6  00 00 00 00 - 07 28 C9 B6  3E 61 00 00 .........(..>a..
08193F34 : 38 40 19 08  00 00 00 00 - 1C 40 19 08  5B 25 D4 B6 8@.......@..[%..
[007B:0819401C]---------------------------------------------------------[ data]
0819401C : 80 DA D4 B6  3E 61 00 00 - FF FF FF FF  FF FF FF FF ....>a..........
0819402C : F4 0F CF B6  00 00 00 00 - B8 40 19 08  88 40 19 08 .........@...@..
[0073:B7F13410]---------------------------------------------------------[ code]
0xb7f13410 <__kernel_vsyscall+16>:	pop    %ebp
0xb7f13411 <__kernel_vsyscall+17>:	pop    %edx
0xb7f13412 <__kernel_vsyscall+18>:	pop    %ecx
0xb7f13413 <__kernel_vsyscall+19>:	ret    
0xb7f13414:	nop    
0xb7f13415:	nop    
------------------------------------------------------------------------------
0xb7f13410 in __kernel_vsyscall ()
  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 226
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 197
  • #8 <signal handler called>
  • #9 ephy_node_emit_signal
    at ephy-node.c line 183
  • #10 child_changed
    at ephy-node.c line 429
  • #11 IA__g_hash_table_foreach
    at ghash.c line 1067
  • #12 ephy_node_set_property
    at ephy-node.c line 464
  • #13 resolver_found_cb
    at ephy-bookmarks.c line 975
  • #14 ga_signals_marshal_VOID__INT_ENUM_STRING_STRING_STRING_STRING_POINTER_INT_POINTER_INT
    at signals-marshal.c line 89
  • #15 IA__g_closure_invoke
    at gclosure.c line 490
  • #16 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #17 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #18 IA__g_signal_emit
    at gsignal.c line 2243
  • #19 _avahi_service_resolver_cb
    at ga-service-resolver.c line 326
  • #20 avahi_service_resolver_event
    at resolver.c line 148
  • #21 filter_func
    at client.c line 256
  • #22 dbus_connection_dispatch
    at dbus-connection.c line 4379
  • #23 dispatch_timeout_callback
    at ../avahi-common/dbus-watch-glue.c line 107
  • #24 dispatch_func
    at glib-watch.c line 254
  • #25 IA__g_main_context_dispatch
    at gmain.c line 2003
  • #26 g_main_context_iterate
    at gmain.c line 2636
  • #27 IA__g_main_loop_run
    at gmain.c line 2844
  • #28 IA__gtk_main
    at gtkmain.c line 1163
  • #29 main
    at ephy-main.c line 737


----------- .xsession-errors (1850 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Reinout van Schouwen 2008-03-14 10:01:05 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 516008 ***