Bug 349820 – crash on Epiphany Web Bookmarks

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 349820 - crash on Epiphany Web Bookmarks


Summary:	crash on Epiphany Web Bookmarks


Status:	RESOLVED DUPLICATE of bug 354790

Product:	epiphany
Classification:	Core
Component:	General
Version:	2.15.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-08-03 18:15 UTC by Brian Kerrick Nickel
Modified:	2006-12-17 17:40 UTC

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

Description Brian Kerrick Nickel 2006-08-03 18:15:05 UTC

What were you doing when the application crashed?
Clicked on the "Source Tarball" icon at http://www.jokosher.org/download/


Distribution: Gentoo Base System version 1.12.4
Gnome Release: 2.15.90 2006-07-27 (Gentoo)
BugBuddy Version: 2.15.90

Memory status: size: 225603584 vsize: 0 resident: 225603584 share: 0 rss: 85168128 rss_rlim: 0
CPU usage: start_time: 1154619719 rtime: 0 utime: 59524 stime: 0 cutime:56050 cstime: 0 timeout: 3474 it_real_value: 0 frequency: 43

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

(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 -1231554016 (LWP 12543)]
[New Thread -1357907040 (LWP 19649)]
[New Thread -1339303008 (LWP 19648)]
[New Thread -1374692448 (LWP 12615)]
[New Thread -1330046048 (LWP 12548)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 69943

Thread 1 (Thread -1231554016 (LWP 12543))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_return_if_fail_warning
from /usr/lib/libglib-2.0.so.0
#10 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#11 NSGetModule
from /usr/lib/mozilla-firefox/components/libgkplugin.so
#12 NSGetModule
from /usr/lib/mozilla-firefox/components/libgkplugin.so
#13 ??
from /usr/lib/mozilla-firefox/components/libgkplugin.so
#14 ??
#15 ??
from /usr/lib/mozilla-firefox/components/libgklayout.so
#16 ??
#17 NSGetModule
from /usr/lib/mozilla-firefox/components/libgklayout.so
#18 NSGetModule
from /usr/lib/mozilla-firefox/components/libgklayout.so
#19 NSGetModule
from /usr/lib/mozilla-firefox/components/libgklayout.so
#20 NSGetModule
from /usr/lib/mozilla-firefox/components/libgkplugin.so
#21 NSGetModule
from /usr/lib/mozilla-firefox/components/libgkplugin.so
#22 nsCOMPtr_base::~nsCOMPtr_base
from /usr/lib/mozilla-firefox/libxpcom_core.so
#23 ??
from /usr/lib/mozilla-firefox/components/libgkplugin.so
#24 ??
#25 __malloc_initialize_hook
from /lib/libc.so.6
#26 ??
#27 ??
from /usr/lib/mozilla-firefox/components/libgkplugin.so
#28 ??
#29 ??
#30 ??
#31 ??
from /usr/lib/mozilla-firefox/components/libgkplugin.so
#32 ??
#33 ??
from /usr/lib/mozilla-firefox/components/libgkplugin.so
#34 ??
#35 ??
from /usr/lib/mozilla-firefox/components/libgkplugin.so
#36 ??
#37 ??
from /usr/lib/mozilla-firefox/libxpcom_core.so
#38 ??
#39 nsSupportsWeakReference::GetWeakReference
from /usr/lib/mozilla-firefox/libxpcom_core.so
#0 __kernel_vsyscall

Comment 1 Wouter Bolsterlee (uws) 2006-08-14 07:34:54 UTC

Looks like a Mozilla issue...

Comment 2 Christian Persch 2006-08-14 10:44:57 UTC

I suspect it's bug https://bugzilla.mozilla.org/show_bug.cgi?id=241535 .

Comment 3 Reinout van Schouwen 2006-12-17 17:40:17 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 354790 ***