Bug 356229 – crash in Epiphany Web Browser: Closing 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 356229 - crash in Epiphany Web Browser: Closing epiphany


Summary:	crash in Epiphany Web Browser: Closing epiphany


Status:	RESOLVED DUPLICATE of bug 348397

Product:	epiphany
Classification:	Core
Component:	General
Version:	2.16.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-09-16 06:40 UTC by Baptiste Mille-Mathias
Modified:	2006-09-16 18:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Baptiste Mille-Mathias 2006-09-16 06:40:32 UTC

Version: 2.16.0

What were you doing when the application crashed?
Closing epiphany


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 122269696 vsize: 0 resident: 122269696 share: 0 rss: 54620160 rss_rlim: 0
CPU usage: start_time: 1158388553 rtime: 0 utime: 4409 stime: 0 cutime:4183 cstime: 0 timeout: 226 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209500800 (LWP 5151)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 72468

Thread 1 (Thread -1209500800 (LWP 5151))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 gtk_moz_embed_get_title
from /usr/lib/firefox/libgtkembedmoz.so
#4 <signal handler called>
#5 ??
#6 ??
from /usr/lib/libglib-2.0.so.0
#7 pthread_mutex_lock
from /lib/tls/i686/cmov/libc.so.6
#8 g_timeout_dispatch
at gmain.c line 3422
#9 IA__g_main_context_dispatch
at gmain.c line 2045
#10 g_main_context_iterate
at gmain.c line 2677
#11 IA__g_main_loop_run
at gmain.c line 2881
#12 IA__gtk_main
at gtkmain.c line 1024
#13 main
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-09-16 11:14:37 UTC

Baptiste, seems to be the same crahs again you reported before. :)

Closing epiphany, you say... Would this happen to be the same or a similar site (with plugin) for this crash, by any chance?

For some strange reason, bug 348397 has been closed incomplete. Baptiste, please feel free to reopen bug 348397 if you still can reproduce the issue, or reopen this one, if you seriously believe they are not related. Looks to be the same, though.


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

Comment 2 Christian Persch 2006-09-16 14:16:56 UTC

It's not Baptiste's fault that this is a dup, I'd say it's bug-buddy's fault: it should check if it has submitted a crash with the same trace before for the same program version (someone open a RFE for bb?) :)

Comment 3 Baptiste Mille-Mathias 2006-09-16 15:58:23 UTC

Sorry, I had to left when I closed epi, and didn't had time to check for a dup.

Comment 4 Karsten Bräckelmann 2006-09-16 18:54:05 UTC

Nah, I did not say it is anybodys fault. Filing duplicates happens to all of us. No need to be sorry, Baptiste. :)

Christian, there is no way bug-buddy could check that *reliably*. In this case it is the same crash, but the stacktraces are not bitwise identical. This kind of judgement should be done by the developers and bugsquad (sic ;-). Had this discussion already... But I digress. ;)