Bug 578343 – crash in Epiphany Web Browser: closing window

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 578343 - crash in Epiphany Web Browser: closing window


Summary:	crash in Epiphany Web Browser: closing window


Status:	RESOLVED DUPLICATE of bug 532370

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-04-08 08:21 UTC by eric
Modified:	2009-04-08 12:31 UTC

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

Description eric 2009-04-08 08:21:29 UTC

Version: 2.24.3

What were you doing when the application crashed?
closing window


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.24.3 2009-03-30 (Gentoo)
BugBuddy Version: 2.24.2

System: Linux 2.6.28-tuxonice-r8 #1 SMP Mon Mar 23 05:23:43 CET 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 132169728 vsize: 132169728 resident: 64712704 share: 26722304 rss: 64712704 rss_rlim: 18446744073709551615
CPU usage: start_time: 1239177815 rtime: 6067 utime: 5329 stime: 738 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 0xb5a4c730 (LWP 17581)]
0xb7fef424 in __kernel_vsyscall ()

+ Trace 214282

Thread 1 (Thread 0xb5a4c730 (LWP 17581))

#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 check_if_gdb
at gnome-breakpad.cc line 223
#5 bugbuddy_segv_handle
at gnome-breakpad.cc line 84
#6 nsProfileLock::FatalSignalHandler
at nsProfileLock.cpp line 216
#7 <signal handler called>
#8 ??
#9 NS_HasPendingEvents_P
at nsThreadUtils.cpp line 207
#10 nsBaseAppShell::OnProcessNextEvent
at nsBaseAppShell.cpp line 288
#11 nsThread::ProcessNextEvent
at nsThread.cpp line 497
#12 NS_ProcessPendingEvents_P
at nsThreadUtils.cpp line 180
#13 nsBaseAppShell::NativeEventCallback
at nsBaseAppShell.cpp line 121
#14 nsAppShell::EventProcessorCallback
at nsAppShell.cpp line 69
#15 g_io_unix_dispatch
#16 g_main_dispatch
at gmain.c line 2144
#17 g_main_context_iterate
at gmain.c line 2697
#18 IA__g_main_loop_run
at gmain.c line 2986
#19 IA__gtk_main
at gtkmain.c line 1200
#20 main
at ephy-main.c line 749
#0 __kernel_vsyscall



----------- .xsession-errors (1232 sec old) ---------------------
icemon: slotCheckScheduler
ignoring localhost lo
broadcast eth1 10.64.255.255
ignoring localhost lo
broadcast eth1 10.64.255.255
icemon: slotCheckScheduler
scheduler is on 10.64.65.142:8765 (net ICECREAM)
(evolution:7812): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:7812): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:7812): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:7812): camel-WARNING **: camel_exception_get_id called with NULL parameter.
--------------------------------------------------

Comment 1 palfrey 2009-04-08 12:31:37 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 532370 ***