Bug 540060 – crash in Epiphany Web Browser (Gecko):

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 540060 - crash in Epiphany Web Browser (Gecko):


Summary:	crash in Epiphany Web Browser (Gecko):


Status:	RESOLVED DUPLICATE of bug 537495

Product:	epiphany
Classification:	Core
Component:	[obsolete] BugBuddyBugs
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-24 23:11 UTC by nethunter+gnome
Modified:	2008-06-25 17:57 UTC

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

Description nethunter+gnome 2008-06-24 23:11:50 UTC

Version: 2.22.1.1

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-NetHunt #19 SMP Sat Jun 14 15:09:38 IDT 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Aurora
Icon Theme: Discovery

Memory status: size: 794075136 vsize: 794075136 resident: 149573632 share: 35778560 rss: 149573632 rss_rlim: 18446744073709551615
CPU usage: start_time: 1214336838 rtime: 22896 utime: 19247 stime: 3649 cutime:5 cstime: 14 timeout: 0 it_real_value: 0 frequency: 100

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

(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 0x7f5d57b92780 (LWP 816)]
[New Thread 0x421e1950 (LWP 25955)]
[New Thread 0x44695950 (LWP 25727)]
[New Thread 0x43693950 (LWP 11964)]
[New Thread 0x43e94950 (LWP 11963)]
[New Thread 0x419e0950 (LWP 822)]
[New Thread 0x40927950 (LWP 817)]
(no debugging symbols found)
0x00007f5d501d2edf in waitpid () from /lib/libpthread.so.0

+ Trace 201311

Thread 1 (Thread 0x7f5d57b92780 (LWP 816))

#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 dbus_g_proxy_connect_signal
from /usr/lib/libdbus-glib-1.so.2
#7 notify_notification_show
from /usr/lib/libnotify.so.1
#8 ??
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 ??
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#13 ??
#14 ??
from /usr/lib/libxul.so.0d
#15 ??
from /usr/lib/libxul.so.0d
#16 ??
from /usr/lib/libxul.so.0d
#17 ??
from /usr/lib/libxul.so.0d
#18 ??
from /usr/lib/libxul.so.0d
#19 ??
from /usr/lib/libxul.so.0d
#20 ??
from /usr/lib/libxul.so.0d
#21 PL_HandleEvent
from /usr/lib/libxul.so.0d
#22 PL_ProcessPendingEvents
from /usr/lib/libxul.so.0d
#23 ??
from /usr/lib/libxul.so.0d
#24 ??
from /usr/lib/libxul.so.0d
#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



----------- .xsession-errors (38070 sec old) ---------------------
** Message: Failed connection to device on 00:19:79:CE:88:7C
** Message: Exiting connect thread
** Message: Auto-retrying the connection
** Message: New connection device is 00:19:79:CE:88:7C (not changed)
** Message: New connection device is 00:19:79:CE:88:7C (not changed)
** Message: Connecting...
** Message: Status 1
** Message: Making serial port connection
** Message: Failed connection to device on 00:19:79:CE:88:7C
** Message: Exiting connect thread
** Message: Auto-retrying the connection
** Message: New connection device is 00:19:79:CE:88:7C (not changed)
** Message: New connection device is 00:19:79:CE:88:7C (not changed)
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-06-25 17:57: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 537495 ***