GNOME Bugzilla – Bug 356632
crash on print with fontconfig 2.4 [@FcCharSetDestroy - ~nsFontMetricsPS]
Last modified: 2008-01-13 16:55:28 UTC
Version: 2.14.3 What were you doing when the application crashed? Printing using CUPS (Firefox 2.0 CVS build from around 20060917 Distribution: Gentoo Base System version 1.12.5 Gnome Release: 2.16.0 2006-09-17 (Gentoo) BugBuddy Version: 2.16.0 Memory status: size: 184217600 vsize: 0 resident: 184217600 share: 0 rss: 41451520 rss_rlim: 0 CPU usage: start_time: 1158619893 rtime: 0 utime: 337 stime: 0 cutime:317 cstime: 0 timeout: 20 it_real_value: 0 frequency: 0 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 -1230951904 (LWP 5771)] [New Thread -1328665696 (LWP 5778)] [New Thread -1320272992 (LWP 5777)] [New Thread -1311880288 (LWP 5776)] [New Thread -1303487584 (LWP 5775)] [New Thread -1294464096 (LWP 5774)] [New Thread -1285960800 (LWP 5773)] [New Thread -1253962848 (LWP 5772)] _______________________________________________________________________________ eax:FFFFFE00 ebx:00001699 ecx:BFA25198 edx:00000000 eflags:00200293 esi:08AAD480 edi:0000000B esp:BFA250B4 ebp:BFA251A8 eip:FFFFE410 cs:0073 ds:007B es:007B fs:0000 gs:0033 ss:007B o d I t S z A p C [007B:BFA250B4]---------------------------------------------------------[stack] BFA250E4 : 4C A7 F6 B7 18 51 A2 00 - 00 00 00 00 00 00 00 00 L....Q.......... BFA250D4 : 98 51 A2 BF 00 00 00 00 - 80 51 A2 BF B8 E4 F7 B7 .Q.......Q...... BFA250C4 : 74 1A E5 B7 00 00 00 00 - C5 D9 E1 B7 99 16 00 00 t............... BFA250B4 : A8 51 A2 BF 00 00 00 00 - 98 51 A2 BF DB BF ED B6 .Q.......Q...... [007B:08AAD480]---------------------------------------------------------[ data] 08AAD480 : A0 65 97 08 00 00 00 00 - E8 8D D6 B6 C8 D4 AA 08 .e.............. 08AAD490 : 38 00 00 00 05 00 00 00 - E8 8D D6 B6 D0 6F 98 08 8............o.. [0073:FFFFE410]---------------------------------------------------------[ code] 0xffffe410 <__kernel_vsyscall+16>: pop %ebp 0xffffe411 <__kernel_vsyscall+17>: pop %edx 0xffffe412 <__kernel_vsyscall+18>: pop %ecx 0xffffe413 <__kernel_vsyscall+19>: ret 0xffffe414 <__kernel_vsyscall+20>: nop 0xffffe415 <__kernel_vsyscall+21>: nop ------------------------------------------------------------------------------ 0xffffe410 in __kernel_vsyscall ()
+ Trace 72693
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Could you also please try to reproduce the problem with Mozilla? This is possibly the same bug as https://bugzilla.mozilla.org/show_bug.cgi?id=294879.
Actually I'm in the process of reinstallation at the moment - so not really able to do a stack trace. However, I can confirm that Firefox exhibits the behaviour described in the bug above. My reason for trying Epiphany was to actually print without the crash - but it seems ff and underlying libraries are affected. Should this be marked as resolved upstream?
*** Bug 356812 has been marked as a duplicate of this bug. ***
Vladimir: thanks, resolving.
*** Bug 356544 has been marked as a duplicate of this bug. ***
Which version is the fontconfig library on your systems? Good trace from the latest dup:
+ Trace 72989
-> https://bugzilla.mozilla.org/show_bug.cgi?id=294879
*** Bug 357222 has been marked as a duplicate of this bug. ***
*** Bug 357350 has been marked as a duplicate of this bug. ***
*** Bug 357766 has been marked as a duplicate of this bug. ***
Can someone who got the crash please run epiphany under valgrind, load a web page and print-to-file until it crashes again, then attach the log file here? export G_SLICE=always-malloc export G_DEBUG=gc-friendly,resident-modules export MALLOC_CHECK_=1 valgrind --tool=memcheck --log-file=report --num-callers=24 --leak-check=yes --error-limit=no `which epiphany` -p --sm-disable
No further info needed, upstream has identified the problem.
*** Bug 358131 has been marked as a duplicate of this bug. ***
*** Bug 359400 has been marked as a duplicate of this bug. ***
*** Bug 360160 has been marked as a duplicate of this bug. ***
*** Bug 360177 has been marked as a duplicate of this bug. ***
Bug #360492 seems like a dup, it has a longer trace so I didn't marked it as dup. Check it out.
*** Bug 360492 has been marked as a duplicate of this bug. ***
*** Bug 361355 has been marked as a duplicate of this bug. ***
*** Bug 361485 has been marked as a duplicate of this bug. ***
*** Bug 361976 has been marked as a duplicate of this bug. ***
*** Bug 362740 has been marked as a duplicate of this bug. ***
*** Bug 361110 has been marked as a duplicate of this bug. ***
*** Bug 363716 has been marked as a duplicate of this bug. ***
*** Bug 364558 has been marked as a duplicate of this bug. ***
*** Bug 364665 has been marked as a duplicate of this bug. ***
*** Bug 365704 has been marked as a duplicate of this bug. ***
*** Bug 369804 has been marked as a duplicate of this bug. ***
*** Bug 370126 has been marked as a duplicate of this bug. ***
*** Bug 370825 has been marked as a duplicate of this bug. ***
*** Bug 372368 has been marked as a duplicate of this bug. ***
*** Bug 372506 has been marked as a duplicate of this bug. ***
*** Bug 373487 has been marked as a duplicate of this bug. ***
*** Bug 374630 has been marked as a duplicate of this bug. ***
*** Bug 376919 has been marked as a duplicate of this bug. ***
*** Bug 377148 has been marked as a duplicate of this bug. ***
*** Bug 377345 has been marked as a duplicate of this bug. ***
*** Bug 377526 has been marked as a duplicate of this bug. ***
*** Bug 378494 has been marked as a duplicate of this bug. ***
*** Bug 379999 has been marked as a duplicate of this bug. ***
*** Bug 381032 has been marked as a duplicate of this bug. ***
*** Bug 384757 has been marked as a duplicate of this bug. ***
*** Bug 385003 has been marked as a duplicate of this bug. ***
*** Bug 385113 has been marked as a duplicate of this bug. ***
*** Bug 385171 has been marked as a duplicate of this bug. ***
*** Bug 378939 has been marked as a duplicate of this bug. ***
*** Bug 395841 has been marked as a duplicate of this bug. ***
*** Bug 390223 has been marked as a duplicate of this bug. ***
*** Bug 388698 has been marked as a duplicate of this bug. ***
*** Bug 405172 has been marked as a duplicate of this bug. ***
*** Bug 401910 has been marked as a duplicate of this bug. ***
*** Bug 405499 has been marked as a duplicate of this bug. ***
*** Bug 406612 has been marked as a duplicate of this bug. ***
*** Bug 408896 has been marked as a duplicate of this bug. ***
*** Bug 409453 has been marked as a duplicate of this bug. ***
*** Bug 414071 has been marked as a duplicate of this bug. ***
*** Bug 423871 has been marked as a duplicate of this bug. ***
*** Bug 423859 has been marked as a duplicate of this bug. ***
*** Bug 415882 has been marked as a duplicate of this bug. ***
*** Bug 415883 has been marked as a duplicate of this bug. ***
*** Bug 419530 has been marked as a duplicate of this bug. ***
*** Bug 423844 has been marked as a duplicate of this bug. ***
*** Bug 426219 has been marked as a duplicate of this bug. ***
*** Bug 429564 has been marked as a duplicate of this bug. ***
I'm the reporter of bug 429564. It has a long backtrace (bug 360492 too). The issue occurred compiling Epiphany 2.18.0 against XULRunner 1.8.0.4. Recompiling it against Firefox 2.0.0.3 solved the issue. Do you still need someone to install valgrind and reproduce the crash?
No need to, no. This is a mozilla bug (see comment 7), and it's fixed. It's just that some distributions still haven't managed to ship the fix yet.
Thanks, I just posted a comment on XULRunner stabilization in Gentoo: http://bugs.gentoo.org/show_bug.cgi?id=170101#c6
*** Bug 431584 has been marked as a duplicate of this bug. ***
*** Bug 431760 has been marked as a duplicate of this bug. ***
*** Bug 439238 has been marked as a duplicate of this bug. ***
*** Bug 434715 has been marked as a duplicate of this bug. ***
*** Bug 445978 has been marked as a duplicate of this bug. ***
*** Bug 459394 has been marked as a duplicate of this bug. ***
*** Bug 462093 has been marked as a duplicate of this bug. ***
*** Bug 468145 has been marked as a duplicate of this bug. ***
*** Bug 469974 has been marked as a duplicate of this bug. ***
*** Bug 480389 has been marked as a duplicate of this bug. ***
*** Bug 470231 has been marked as a duplicate of this bug. ***