GNOME Bugzilla – Bug 385635
[pyxpcom] crash on shutdown with pyxpcom
Last modified: 2009-02-28 16:31:53 UTC
Version: 2.16.1 What were you doing when the application crashed? Closing the epiphany window, which had one tab open. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 187371520 vsize: 0 resident: 187371520 share: 0 rss: 67887104 rss_rlim: 0 CPU usage: start_time: 1166047828 rtime: 0 utime: 2285 stime: 0 cutime:2212 cstime: 0 timeout: 73 it_real_value: 0 frequency: 7 Backtrace was generated from '/usr/bin/epiphany' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1229039952 (LWP 31994)] [New Thread -1351140448 (LWP 32419)] [New Thread -1290945632 (LWP 32002)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 93962
Thread 1 (Thread -1229039952 (LWP 31994))
This is a real bug in Epiphany ('bad interaction in ephy with xpcom startup and python gc' according to chpe), marking NEW.
*** Bug 359736 has been marked as a duplicate of this bug. ***
Bug 359736 contains a pretty good stacktrace.
Ubuntu bug about that: https://launchpad.net/epiphany-browser/+bug/86006
*** Bug 436608 has been marked as a duplicate of this bug. ***
bug 436608 also has a good trace.
*** Bug 444470 has been marked as a duplicate of this bug. ***
*** Bug 480928 has been marked as a duplicate of this bug. ***
Gecko only, closing as WONTFIX.