Get the latest tech news

Memory safety for web fonts


Learn how and why the Chrome team has replaced FreeType with Skrifa.

This pattern of problems is not unique to FreeType, we observe that other unsafe libraries admit issues even when we use the best software engineers we can find, code review every change, and require tests. Dependency issuesFuzzing isn't enough Fuzzing–automated testing with a wide range of inputs, including randomized invalid ones–is meant to find many of the types of issues that get into the stable release of Chrome. Use of grammar- or structure-aware mutators might help avoid production of variants that are rejected early, at the cost of taking more time to develop, and introducing chances which miss parts of the search space.

Get the Android app

Or read this on Hacker News

Read more on:

Photo of Memory Safety

Memory Safety

Photo of Web Fonts

Web Fonts

Related news:

News photo

How does Ada's memory safety compare against Rust?

News photo

Memory safety without lifetime parameters

News photo

Advancing Memory Safety