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 440538 - crash in Epiphany Web Browser: Closing Epiphany window.
crash in Epiphany Web Browser: Closing Epiphany window.
Status: RESOLVED DUPLICATE of bug 349051
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-05-22 19:22 UTC by Nil Gradisnik
Modified: 2007-05-22 22:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Nil Gradisnik 2007-05-22 19:22:01 UTC
Version: 2.16.3

What were you doing when the application crashed?
Closing Epiphany window.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2948.fc6 #1 SMP Fri Apr 27 19:48:40 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled

Memory status: size: 399384576 vsize: 0 resident: 399384576 share: 0 rss: 79319040 rss_rlim: 0
CPU usage: start_time: 1179840293 rtime: 0 utime: 35711 stime: 0 cutime:33397 cstime: 0 timeout: 2314 it_real_value: 0 frequency: 3899

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 -1208817952 (LWP 27355)]
[New Thread -1496974448 (LWP 1694)]
[New Thread -1434035312 (LWP 1693)]
[New Thread -1538933872 (LWP 1692)]
[New Thread -1486484592 (LWP 838)]
[New Thread -1284207728 (LWP 27387)]
[New Thread -1273717872 (LWP 27386)]
[New Thread -1223136368 (LWP 27357)]
[New Thread -1212646512 (LWP 27356)]
(no debugging symbols found)
0x001ca402 in __kernel_vsyscall ()

Thread 1 (Thread -1208817952 (LWP 27355))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 nsSupportsWeakReference::~nsSupportsWeakReference\$base
    from /usr/lib/firefox-2.0.0.3/libgtkembedmoz.so
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (24298 sec old) ---------------------
(trackerd:2643): Pango-WARNING **: pango_get_log_attrs: attrs_len should have been at least 44, but was 70.  Expect corrupted memory.
(trackerd:2643): Pango-WARNING **: pango_get_log_attrs: attrs_len should have been at least 35, but was 39.  Expect corrupted memory.
(trackerd:2643): Pango-WARNING **: pango_get_log_attrs: attrs_len should have been at least 35, but was 43.  Expect corrupted memory.
(trackerd:2643): Pango-WARNING **: pango_get_log_attrs: attrs_len should have been at least 36, but was 42.  Expect corrupted memory.
(trackerd:2643): Pango-WARNING **: pango_get_log_attrs: attrs_len should have been at least 36, but was 46.  Expect corrupted memory.
(trackerd:2643): Pango-WARNING **: pango_get_log_attrs: attrs_len should have been at least 43, but was 63.  Expect corrupted memory.
(trackerd:2643): Pango-WARNING **: pango_get_log_attrs: attrs_len should have been at least 54, but was 100.  Expect corrupted memory.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Reinout van Schouwen 2007-05-22 22:51:34 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 349051 ***