Shameless plug - while I don't actively do anything with font validator at the
moment / in the near future, it probably is useful for some "mildly broken"
fonts to see why they are broken, and still have some advantages over a few
other font checking tools.
The next major FontVal update (hopefully) is a FontVal-RX release, to make
freetype optional with "alternative rasterizer(s)".
On Saturday 7 February 2026 at 19:18:15 GMT, Alexei Podtelezhnikov
<[email protected]> wrote:
Hi Hiromi
Of all your files only 21_broken.ttf is obviously broken. You information is
interesting but impossible to reproduce without detailed instructions and
backytaces.
Please file separate contained reports, one issue at a time. You need to write
a small program to reproduce the crashes. Or, alternatively, try to crash our
demo programs ftview, ftmulti, ftgrid, ftstring, ftdump, ftlint.
So far I was able to examine all you fonts without errors, except one. Please
understand that Firefox crashes belong to Firefox until you can demonstrate
them separately.
Alexei
> On Feb 7, 2026, at 12:11, Werner LEMBERG <[email protected]> wrote:
>
>
>> I made a few font files the will cause 2 segmentation faults and 1
>> endless loop. [...]
>
> Thanks, will have a look soon. Does this crash with the current
> FreeType development version?
>
>> There is zip file with 18 mb and the password is 12345
>
> The next time, please do not send such large attachments to our
> mailing lists! Instead, you should open an issue in our tracker at
>
> https://gitlab.freedesktop.org/freetype/freetype/-/issues
>
> where you can also set the confidentiality flag if necessary.
>
>
> Werner
>
