https://bugzilla.redhat.com/show_bug.cgi?id=1993670
a3emdot <andre.ma...@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(p...@redhat.com)
--- Comment #14 from a3emdot <andre.ma...@gmx.de> ---
I can finally reproduce the segfaults with the help of valgrind on Fedora 34
$ ./pango-view-segfaults-20210917.sh > pango-view-segfaults-20210917.txt 2>&1
where one can find the following in the written txt file
---
pango-view: cairo-hash.c:217: _cairo_hash_table_destroy: Assertion
`hash_table->live_entries == 0' failed.
==8093==
==8093== Process terminating with default action of signal 6 (SIGABRT): dumping
core
==8093== at 0x4D932A2: raise (in /usr/lib64/libc-2.33.so)
==8093== by 0x4D7C8A3: abort (in /usr/lib64/libc-2.33.so)
==8093== by 0x4D7C788: __assert_fail_base.cold (in /usr/lib64/libc-2.33.so)
==8093== by 0x4D8BA15: __assert_fail (in /usr/lib64/libc-2.33.so)
==8093== by 0x4C642EF: ??? (in /usr/lib64/libcairo.so.2.11704.0)
==8093== by 0x4C64A0A: cairo_debug_reset_static_data (in
/usr/lib64/libcairo.so.2.11704.0)
==8093== by 0x111E2C: ??? (in /usr/bin/pango-view)
==8093== by 0x10EAF6: ??? (in /usr/bin/pango-view)
==8093== by 0x4D7DB74: (below main) (in /usr/lib64/libc-2.33.so)
==8093==
==8093== Process terminating with default action of signal 11 (SIGSEGV)
==8093== General Protection Fault
==8093== at 0x5493C82: __pthread_once_slow (in
/usr/lib64/libpthread-2.33.so)
==8093== by 0x4E8603E: __rpc_thread_variables.part.0 (in
/usr/lib64/libc-2.33.so)
==8093== by 0x4EC861C: free_mem (in /usr/lib64/libc-2.33.so)
==8093== by 0x4EC8271: __libc_freeres (in /usr/lib64/libc-2.33.so)
==8093== by 0x48351E7: _vgnU_freeres (vg_preloaded.c:74)
==8093==
==8093== HEAP SUMMARY:
==8093== in use at exit: 1,226,659 bytes in 20,130 blocks
==8093== total heap usage: 37,522 allocs, 17,392 frees, 5,374,996 bytes
allocated
==8093==
==8093== LEAK SUMMARY:
==8093== definitely lost: 151,552 bytes in 585 blocks
==8093== indirectly lost: 208,373 bytes in 8,421 blocks
==8093== possibly lost: 1,947 bytes in 9 blocks
==8093== still reachable: 861,435 bytes in 11,079 blocks
==8093== suppressed: 0 bytes in 0 blocks
==8093== Rerun with --leak-check=full to see details of leaked memory
==8093==
==8093== For lists of detected and suppressed errors, rerun with: -s
==8093== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
---
$ uname -a
Linux localhost.localdomain 5.13.15-200.fc34.x86_64 #1 SMP Wed Sep 8 15:51:46
UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ dnf list installed | grep pango
pango.i686 1.48.10-1.fc34
@updates
pango.x86_64 1.48.10-1.fc34
@updates
pango-devel.x86_64 1.48.10-1.fc34
@updates
pangomm.x86_64 2.46.1-1.fc34
@updates
$ dnf list installed | grep roboto
google-roboto-condensed-fonts.noarch 2.138-8.fc34
@fedora
google-roboto-fonts.noarch 2.138-8.fc34
@fedora
I would have liked to use the pango-view tool for a font rendering validation
tool
but the segfaults make it totally useless here.
It also looks like the segfaulting behavior depends on the font to be used.
Using "DejaVu Sans" instead of "Roboto Condensed" I don't get the segfaults
with the newer reproducing shell script.
So could we please reopen this issue?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1993670
_______________________________________________
fonts-bugs mailing list -- fonts-bugs@lists.fedoraproject.org
To unsubscribe send an email to fonts-bugs-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/fonts-bugs@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
