Bug 406612 – crash in Epiphany: I was trying to 'print t...

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 406612 - crash in Epiphany: I was trying to 'print t...


Summary:	crash in Epiphany: I was trying to 'print t...


Status:	RESOLVED DUPLICATE of bug 356632

Product:	epiphany
Classification:	Core
Component:	General
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Epiphany Maintainers
QA Contact:	Marco Pesenti Gritti

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-11 05:51 UTC by neil_forwards
Modified:	2007-02-11 11:40 UTC

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

Description neil_forwards 2007-02-11 05:51:08 UTC

Version: 2.16.1

What were you doing when the application crashed?
I was trying to 'print to file' a document I was reading online.


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 525705216 vsize: 525705216 resident: 27594752 share: 35880960 rss: 63475712 rss_rlim: 1343375360
CPU usage: start_time: 1171172226 rtime: 1305 utime: 1232 stime: 73 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/epiphany'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47448228155376 (LWP 5899)]
[New Thread 1090525504 (LWP 5905)]
[New Thread 1082132800 (LWP 5900)]
(no debugging symbols found)
0x00002b2761de6c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 109713

Thread 1 (Thread 47448228155376 (LWP 5899))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 nsProfileLock::FatalSignalHandler
from /usr/lib64/xulrunner-1.8.1b2/libgtkembedmoz.so
#3 <signal handler called>
#4 FcCharSetDestroy
from /usr/lib64/libfontconfig.so.1
#5 nsFontMetricsPS::~nsFontMetricsPS
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#6 nsFontPSAFM::FindFont
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#7 nsFontCache::Flush
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#8 nsFontCache::~nsFontCache
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#9 nsFontCachePS::~nsFontCachePS
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#10 DeviceContextImpl::~DeviceContextImpl
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#11 nsDeviceContextPS::~nsDeviceContextPS
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#12 DeviceContextImpl::Release
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#13 nsPrintData::~nsPrintData
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#14 nsPrintEngine::Destroy
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#15 DocumentViewerImpl::OnDonePrinting
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#16 PL_HandleEvent
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#17 PL_ProcessPendingEvents
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#18 nsEventQueueImpl::~nsEventQueueImpl
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#19 nsCOMPtr<nsIWidget>::nsCOMPtr
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#20 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#21 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#22 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#23 gtk_main
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#24 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Jean-François Rameau 2007-02-11 11: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 356632 ***