hikari wayland compositor (https://hikari.acmelabs.space)
#29Crash with pango 1.48.3
After updating pango to 1.48.3 hikari launches for a brief moment and crashes right away. No error message thrown, so not much I can report currently.
Only, that reverting to 1.48.2 helps. Not sure who or what is at fault, as openbox works fine with latest pango.
Someone who can reproduce this?
Good around to bisecting this:
8f15d1b320f1d859cc0a1a70c1de3c8092ba6b43 is the first bad commit commit 8f15d1b320f1d859cc0a1a70c1de3c8092ba6b43 Author: Matthias Clasen <mclasen@redhat.com> Date: Tue Aug 18 21:55:58 2020 -0400 Move FcFontMatch and FcFontSort calls to a thread fontconfig is thread-safe, so we can do calls that can take several milliseconds to complete in a thread. This patch does that for FcFontSetMatch and FcFontSetSort. It is a win, at least for FcFontSetSort, since it reduces the time that the main thread spends in pango_fc_patterns_get_font_pattern for i > 0 from around 10 to 6 milliseconds.Which is from this MR https://gitlab.gnome.org/GNOME/pango/-/merge_requests/221/commits
There is a somewhat related bug report on the pango tracker: https://gitlab.gnome.org/GNOME/pango/-/issues/542 Looking at the discussion there I suspect they won't revert this change...
- status set to closed
Got around to test again this issue. It irked me a lot that I didn't hear others having this issue?
Good news: This seems to be resolved. Bad news: I don't know why. Latest pango release worked fine (1.48.5) and for testing purposes I went to back to versions I knew that didn't. Well, now they did. I'm somewhat puzzled, but at least this issue can be closed.
