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 401917 - crash in Epiphany Web Bookmarks: I just closed Epiphany.....
crash in Epiphany Web Bookmarks: I just closed Epiphany.....
Status: RESOLVED DUPLICATE of bug 348421
Product: epiphany
Classification: Core
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2007-01-29 00:31 UTC by Timm
Modified: 2007-01-29 09:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Timm 2007-01-29 00:31:14 UTC
Version: 2.16.1

What were you doing when the application crashed?
I just closed Epiphany.. It was lagging since a long time (probably 2 hours) and now it crashed while closing...

It was never that laggy before and I don't think I can reproduce the crash.

So I don't think this report is any use to you, as I don't have epiphany-dbg installed, sorry :(

the -dbs packages should be standard, I think that would help a lot.

regards


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 198881280 vsize: 0 resident: 198881280 share: 0 rss: 69484544 rss_rlim: 0
CPU usage: start_time: 1169995907 rtime: 0 utime: 62136 stime: 0 cutime:58501 cstime: 0 timeout: 3635 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 -1229109584 (LWP 4869)]
[New Thread -1392419936 (LWP 29750)]
[New Thread -1382302816 (LWP 29749)]
[New Thread -1303483488 (LWP 4999)]
[New Thread -1347552352 (LWP 4998)]
[New Thread -1295090784 (LWP 4877)]
[New Thread -1285518432 (LWP 4876)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1229109584 (LWP 4869))

  • #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 __kernel_vsyscall
  • #6 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #7 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #8 IA__g_logv
  • #9 IA__g_log
  • #10 IA__g_assert_warning
  • #11 dbus_g_proxy_set_interface
    from /usr/lib/libdbus-glib-1.so.2
  • #12 dbus_g_proxy_set_interface
    from /usr/lib/libdbus-glib-1.so.2
  • #13 IA__g_object_unref
    at gobject.c line 1760
  • #14 ??
    from /usr/lib/epiphany/2.16/extensions/librssextension.so
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
    from /usr/lib/libgobject-2.0.so.0
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 IA__g_object_unref
    at gobject.c line 1788
  • #23 IA__g_object_unref
    at gobject.c line 1788
  • #24 ephy_shlib_loader_get_type
  • #25 ephy_loader_release_object
  • #26 ephy_extension_attach_window
  • #27 IA__g_list_foreach
    at glist.c line 495
  • #28 ephy_extensions_manager_load
  • #29 IA__g_object_unref
    at gobject.c line 1760
  • #30 ephy_shell_get_session
  • #31 IA__g_object_unref
    at gobject.c line 1760
  • #32 init_gobject
    from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
  • #33 initgc
    from /usr/lib/libpython2.4.so.1.0
  • #34 PyGC_Collect
    from /usr/lib/libpython2.4.so.1.0
  • #35 ephy_python_schedule_gc
  • #36 g_idle_dispatch
    at gmain.c line 3926
  • #37 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #38 g_main_context_iterate
    at gmain.c line 2677
  • #39 IA__g_main_loop_run
    at gmain.c line 2881
  • #40 IA__gtk_main
    at gtkmain.c line 1024
  • #41 main
  • #0 __kernel_vsyscall

Comment 1 Reinout van Schouwen 2007-01-29 09:11:45 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 348421 ***