> This said, if you got 45 minutes (maximum) to dedicate to it, here
> is an easy reproduction procedure: [...]
Sorry, no. Please try bisecting the FreeType git repository, as
mentioned earlier! This is *much* more efficient and should give you
the exact commit that introduces the problem.
Type
git help bisect
on the command line to get acquainted with bisecting, if necessary.
Werner
_______________________________________________
Freetype mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype
