Bug 526460 – crash in Epiphany Web Browser:

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 526460 - crash in Epiphany Web Browser:


Summary:	crash in Epiphany Web Browser:


Status:	RESOLVED DUPLICATE of bug 516008

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-04-06 08:05 UTC by matthew
Modified:	2008-04-06 14:36 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description matthew 2008-04-06 08:05:30 UTC

Version: 2.22.0

What were you doing when the application crashed?



Distribution: Unknown
Gnome Release: 2.22.0 2008-03-22 (Foresight Linux)
BugBuddy Version: 2.22.0

System: Linux 2.6.23.17-0.0.1.smp.gcc4.1.x86.i686 #1 SMP Fri Mar 14 14:19:36 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 227704832 vsize: 227704832 resident: 96583680 share: 34725888 rss: 96583680 rss_rlim: 4294967295
CPU usage: start_time: 1207468408 rtime: 7060 utime: 6638 stime: 422 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb5af36e0 (LWP 30810)]
[New Thread 0xac5d9b90 (LWP 30903)]
[New Thread 0xb2caeb90 (LWP 30902)]
[New Thread 0xacf0eb90 (LWP 30900)]
[New Thread 0xad70fb90 (LWP 30899)]
[New Thread 0xaf74bb90 (LWP 30823)]
[New Thread 0xaff4cb90 (LWP 30822)]
[New Thread 0xb34afb90 (LWP 30821)]
[New Thread 0xb3cb0b90 (LWP 30812)]
[New Thread 0xb44b1b90 (LWP 30811)]
0xb7f45410 in __kernel_vsyscall ()

+ Trace 194363

Thread 1 (Thread 0xb5af36e0 (LWP 30810))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 google_breakpad::ExceptionHandler::HandleException
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#8 nsProfileLock::FatalSignalHandler
from /usr/lib/xulrunner/libgtkembedmoz.so
#9 <signal handler called>
#10 ephy_node_db_is_immutable
at ephy-node-db.c line 174
#11 resolver_found_cb
at ephy-bookmarks.c line 975
#12 ga_signals_marshal_VOID__INT_ENUM_STRING_STRING_STRING_STRING_POINTER_INT_POINTER_INT
from /usr/lib/libavahi-gobject.so.0
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 ??
from /usr/lib/libgobject-2.0.so.0
#15 ??
#16 ??
#0 __kernel_vsyscall



----------- .xsession-errors (54810 sec old) ---------------------
4/5/2008 5:49:55 PM [Info]: Updated first results for 'r'.
4/5/2008 5:49:55 PM [Info]: Updated first results for 's'.
4/5/2008 5:49:55 PM [Info]: Updated first results for 't'.
4/5/2008 5:49:55 PM [Info]: Updated first results for 'u'.
4/5/2008 5:49:55 PM [Info]: Updated first results for 'v'.
4/5/2008 5:49:55 PM [Info]: Updated first results for 'w'.
4/5/2008 5:49:56 PM [Info]: Updated first results for 'x'.
4/5/2008 5:49:56 PM [Info]: Updated "Applications" Item Source.
4/5/2008 5:49:56 PM [Info]: Updated first results for 'y'.
4/5/2008 5:49:56 PM [Info]: Updated first results for 'a'.
4/5/2008 5:49:56 PM [Info]: Updated first results for 'b'.
4/5/2008 5:49:56 PM [Info]: Updated first results for 'c'.
4/5/2008 5:49:56 PM [Info]: Updated first results for 'd'.
4/5/2008 5:49:56 PM [Info]: Updated first results for 'e'.
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Reinout van Schouwen 2008-04-06 14:36:42 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 516008 ***