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 359468 - crash in Epiphany Web Bookmarks: I hit the close button.....
crash in Epiphany Web Bookmarks: I hit the close button.....
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: 2006-10-04 01:16 UTC by JasSmith
Modified: 2006-10-04 01:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description JasSmith 2006-10-04 01:16:07 UTC 
Version: 2.16.1

What were you doing when the application crashed?
I hit the close button... and from all outside appearances it closed correctly.  Why did this come up?


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

Memory status: size: 230825984 vsize: 0 resident: 230825984 share: 0 rss: 115847168 rss_rlim: 0
CPU usage: start_time: 1159888053 rtime: 0 utime: 11717 stime: 0 cutime:11112 cstime: 0 timeout: 605 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 -1228622160 (LWP 12972)]
[New Thread -1331786848 (LWP 26435)]
[New Thread -1388213344 (LWP 26434)]
[New Thread -1356964960 (LWP 14688)]
[New Thread -1348572256 (LWP 14687)]
[New Thread -1279378528 (LWP 12979)]
[New Thread -1248474208 (LWP 12975)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 74402

Thread 1 (Thread -1228622160 (LWP 12972))

  • #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 *__GI_raise
    from /lib/tls/i686/cmov/libc.so.6
  • #7 *__GI_abort
    from /lib/tls/i686/cmov/libc.so.6
  • #8 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #9 g_log
    from /usr/lib/libglib-2.0.so.0
  • #10 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #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 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #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 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #24 ephy_shlib_loader_get_type
  • #25 ephy_loader_release_object
  • #26 ephy_extension_attach_window
  • #27 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #28 ephy_extensions_manager_load
  • #29 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #30 ephy_shell_get_session
  • #31 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #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_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #37 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #38 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #39 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #40 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #41 main
  • #0 __kernel_vsyscall 






Comment 1


Elijah Newren





          2006-10-04 01:18:23 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.

Matches the stack trace in bug 354458, which has been marked as a duplicate of 348421

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