10 May
2022
10 May
'22
6:29 p.m.
This kind of behavior is very suspicious. FWIW the same test was already reduced by 1c7323b1926dbab4c81fd4b22b04d330459c3748. It seems like that PreloadGlyphs() call causes some kind of memory corruption issue in native or something like that.
Can you try to figure out if that's the case and e.g. whether changing the parameters make the issue go away? Depending on the results we might want to put the test inside an if (0){}, with a small comment explaining the details.