Bug 645400 – crash in Epiphany:

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 645400 - crash in Epiphany:


Summary:	crash in Epiphany:


Status:	RESOLVED DUPLICATE of bug 618355

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-03-21 13:55 UTC by ddd
Modified:	2011-03-21 16:00 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description ddd 2011-03-21 13:55:15 UTC

Version: 2.30.6

What were you doing when the application crashed?



Distribution: Debian 6.0
Gnome Release: 2.30.2 2010-11-12 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-5-686 #1 SMP Wed Jan 12 04:01:41 UTC 2011 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Wasp
Icon Theme: Wasp
GTK+ Modules: gnomebreakpad

Memory status: size: 200507392 vsize: 200507392 resident: 37289984 share: 23191552 rss: 37289984 rss_rlim: 18446744073709551615
CPU usage: start_time: 1300722887 rtime: 69 utime: 62 stime: 7 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 0xaf607b70 (LWP 4108)]
[New Thread 0xaff28b70 (LWP 4107)]
0xb786d424 in __kernel_vsyscall ()

+ Trace 226414

Thread 1 (Thread 0xb43bd760 (LWP 4106))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 ??
from /usr/lib/libwebkit-1.0.so.2
#7 JSObjectSetProperty
from /usr/lib/libwebkit-1.0.so.2
#8 ??
#9 ??
from /usr/lib/libgnome-keyring.so.0
#10 ??
from /usr/lib/libgnome-keyring.so.0
#11 ??
from /usr/lib/libgnome-keyring.so.0
#12 ??
from /usr/lib/libgnome-keyring.so.0
#13 ??
from /usr/lib/libgnome-keyring.so.0
#14 ??
from /usr/lib/libgnome-keyring.so.0
#15 ??
from /usr/lib/libgnome-keyring.so.0
#16 ??
from /lib/libdbus-1.so.3
#17 ??
from /lib/libdbus-1.so.3
#18 dbus_connection_dispatch
from /lib/libdbus-1.so.3
#19 ??
from /usr/lib/libgnome-keyring.so.0
#20 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#21 ??
from /lib/libglib-2.0.so.0
#22 g_main_loop_run
from /lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 main

A debugging session is active.

	Inferior 1 [process 4106] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (7189 sec old) ---------------------
Corrupt JPEG data: bad Huffman code
Corrupt JPEG data: bad Huffman code
Corrupt JPEG data: bad Huffman code
(exe:3104): Gdk-WARNING **: XID collision, trouble ahead
(exe:3104): Gdk-WARNING **: XID collision, trouble ahead
(exe:3104): Gdk-WARNING **: XID collision, trouble ahead
(exe:3104): Gdk-WARNING **: XID collision, trouble ahead
** Message: console message: http://www.google.com.tr/extern_js/f/CgJ0chICdHIrMEU4ACwrMFo4ACwrMA44ACwrMBc4ACwrMDw4ACwrMFE4ACwrMFk4ACwrMAo4AUAdLCswFjgALCswGTgALCswJTjPiAEsKzAqOAAsKzArOAAsKzA1OAAsKzBAOA
** Message: console message: http://www.google.com.tr/extern_js/f/CgJ0chICdHIrMEU4ACwrMFo4ACwrMA44ACwrMBc4ACwrMDw4ACwrMFE4ACwrMFk4ACwrMAo4AUAdLCswFjgALCswGTgALCswJTjPiAEsKzAqOAAsKzArOAAsKzA1OAAsKzBAOA
--------------------------------------------------

Comment 1 Akhil Laddha 2011-03-21 16:00:29 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 bug 618355 ***