Bug 587232 – crash in Epiphany Web Browser: crash on close

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 587232 - crash in Epiphany Web Browser: crash on close


Summary:	crash in Epiphany Web Browser: crash on close


Status:	RESOLVED DUPLICATE of bug 509083

Product:	epiphany
Classification:	Core
Component:	[obsolete] BugBuddyBugs
Version:	2.24.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Epiphany Maintainers
QA Contact:	Epiphany Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-06-28 22:07 UTC by Steven Noonan
Modified:	2009-06-29 02:59 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description Steven Noonan 2009-06-28 22:07:48 UTC

Version: 2.24.3

What were you doing when the application crashed?
crash on close


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.24.3 2009-05-31 (Gentoo)
BugBuddy Version: 2.24.2

System: Linux 2.6.29.5 #2 SMP Mon Jun 22 19:21:57 PDT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: Neu

Memory status: size: 141250560 vsize: 141250560 resident: 59912192 share: 27230208 rss: 59912192 rss_rlim: 18446744073709551615
CPU usage: start_time: 1246226499 rtime: 838 utime: 721 stime: 117 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb5ae6730 (LWP 2179)]
0xb8060424 in __kernel_vsyscall ()

+ Trace 216237

Thread 1 (Thread 0xb5ae6730 (LWP 2179))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 IA__g_spawn_sync
at gspawn.c line 382
#3 IA__g_spawn_command_line_sync
at gspawn.c line 694
#4 run_bug_buddy
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 check_if_gdb
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 bugbuddy_segv_handle
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 nsProfileLock::FatalSignalHandler
at nsProfileLock.cpp line 216
#8 <signal handler called>
#9 ??
#10 NS_HasPendingEvents_P
at nsThreadUtils.cpp line 207
#11 nsBaseAppShell::OnProcessNextEvent
at nsBaseAppShell.cpp line 288
#12 nsThread::ProcessNextEvent
at nsThread.cpp line 497
#13 NS_ProcessPendingEvents_P
at nsThreadUtils.cpp line 180
#14 nsBaseAppShell::NativeEventCallback
at nsBaseAppShell.cpp line 121
#15 nsAppShell::EventProcessorCallback
at nsAppShell.cpp line 69
#16 g_io_unix_dispatch
#17 IA__g_main_context_dispatch
at gmain.c line 2144
#18 g_main_context_iterate
at gmain.c line 2778
#19 IA__g_main_loop_run
at gmain.c line 2986
#20 IA__gtk_main
at gtkmain.c line 1200
#21 main
at ephy-main.c line 749
#0 __kernel_vsyscall



----------- .xsession-errors (144314 sec old) ---------------------
[00000405] access_file access error: read failed (Input/output error)
[00000405] access_file access error: read failed (Input/output error)
[00000405] access_file access error: read failed (Input/output error)
[00000405] access_file access error: read failed (Input/output error)
[00000405] access_file access error: read failed (Input/output error)
[00000405] access_file access error: read failed (Input/output error)
[00000405] access_file access error: read failed (Input/output error)
[00000405] access_file access error: read failed (Input/output error)
[00000405] access_file access error: read failed (Input/output error)
[00000405] access_file access error: read failed (Input/output error)
[00000405] access_file access error: read failed (Input/output error)
[00000405] access_file access error: read failed (Input/output error)
[00000405] access_file access error: read failed (Input/output error)
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2009-06-29 02:59:26 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 ***