Tim Murphy wrote:
Hi,
After installing fontconfig-2.3.91.cvs20051017-1.i386, gdm would start but
then crash before displaying anything. Eventually I managed to get X to
startup with xinit and tried to run metacity. Metacity crashed and I then
tried it under valgrind. I have appended the output but basically there
seemed to be a problem in fontconfig relating to permissions to some mmapp'd
memory area.
I downgraded to fontconfig-2.3.2-1 and the problem "went away."
I can't be sure if this is a fontconfig problem or some setup problem - has
anyone else experienced it?
Regards,
Tim
==23609== Invalid read of size 4
==23609== at 0x1BCEC823: FcStrListCreate (in
/usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x1BCE3661: FcLangSetHasLang (in
/usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x1BCE56FB: (within /usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x1BCE5B3F: (within /usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x1BCE5F7F: (within /usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x1BCE686C: FcFontSetSort (in /usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x1BCE6D72: FcFontSort (in /usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x4C91688D: (within /usr/lib/libpangoft2-1.0.so.0.1001.0)
==23609== by 0x4C94C0AE: pango_font_map_load_fontset (in /usr/lib/libpango-
1.0.so.0.1001.0)
==23609== by 0x4C94ACBA: pango_context_get_metrics (in /usr/lib/libpango-
1.0.so.0.1001.0)
==23609== by 0x807D261: ??? (theme.c:5180)
==23609== by 0x805F196: ??? (frames.c:503)
==23609== Address 0x6D616E20 is not stack'd, malloc'd or (recently) free'd
==23609==
==23609== Process terminating with default action of signal 11 (SIGSEGV)
==23609== Bad permissions for mapped region at address 0x6D616E20
==23609== at 0x1BCEC823: FcStrListCreate (in
/usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x1BCE3661: FcLangSetHasLang (in
/usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x1BCE56FB: (within /usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x1BCE5B3F: (within /usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x1BCE5F7F: (within /usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x1BCE686C: FcFontSetSort (in /usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x1BCE6D72: FcFontSort (in /usr/lib/libfontconfig.so.1.0.4)
==23609== by 0x4C91688D: (within /usr/lib/libpangoft2-1.0.so.0.1001.0)
==23609== by 0x4C94C0AE: pango_font_map_load_fontset (in /usr/lib/libpango-
1.0.so.0.1001.0)
==23609== by 0x4C94ACBA: pango_context_get_metrics (in /usr/lib/libpango-
1.0.so.0.1001.0)
==23609== by 0x807D261: ??? (theme.c:5180)
==23609== by 0x805F196: ??? (frames.c:503)
==23609==
==23609== ERROR SUMMARY: 94 errors from 3 contexts (suppressed: 64 from 3)
==23609== malloc/free: in use at exit: 337686 bytes in 6999 blocks.
==23609== malloc/free: 28615 allocs, 21616 frees, 2031211 bytes allocated.
==23609== For counts of detected errors, rerun with: -v
==23609== searching for pointers to 6999 not-freed blocks.
==23609== checked 792564 bytes.
==23609==
==23609== LEAK SUMMARY:
==23609== definitely lost: 56 bytes in 2 blocks.
==23609== possibly lost: 1084 bytes in 29 blocks.
==23609== still reachable: 336546 bytes in 6968 blocks.
==23609== suppressed: 0 bytes in 0 blocks.
==23609== Use --leak-check=full to see details of leaked memory.
I was having a problem with firefox crashes that were also "fixed" by
downgrading to fontconfig-2.3.2-1, but then the next day after logging
out and back in (and possibly also rebooting) I re-upgraded to
fontconfig-2.3.91.cvs20051017-1 and the problem had gone away.
I suspect some kind of font cache issue during upgrades.
I reported the problem in bug#171224, but later closed it again as I can no longer recreate it.
John
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
