* [glyf] Charge composite offsets to the work budget Composite glyphs prepare component offsets before descending into children. This work was not charged to the shared rendering budget, including offsets for children later skipped by cycle detection. Repeated preparation through COLR extents could time out the shaper. Charge each offset before loading it and restore the scratch length on failure. Add a cyclic-composite budget regression and the minimized fuzzer testcase. The full Meson suite passes (292 passed, one skipped). The reproducer completes under ASan/UBSan in 17 seconds instead of timing out after 60 seconds. A failing-allocation variant passes 100 runs. Fixes: https://oss-fuzz.com/testcase-detail/6193853460447232 Assisted-by: OpenAI Codex * [glyf] Charge component preparation as traversal work Component preparation parses records and updates scratch vectors, but charging one unit per record still allows excessive work within the shared budget. Use the existing 16-unit glyph traversal charge for preparing a component, including children skipped by cycle detection. Increase the cyclic-composite regression's budget so it also catches the undercharged preparation path. The reproducer now takes about 1.1 seconds under ASan/UBSan and 0.03 seconds in the normal build. Tested with the full Meson suite (292 passed, one skipped), 100 sanitizer reproducer runs, and 100 failing-allocation variant runs. Assisted-by: OpenAI Codex
Security Fuzzers
To build the fuzzers with libFuzzer to perform actual fuzzing, build with:
CXX=clang++ CXXFLAGS="-fsanitize=address,fuzzer-no-link" meson fuzzbuild --default-library=static -Dfuzzer_ldflags="-fsanitize=address,fuzzer"
ninja -Cfuzzbuild
Then, run the fuzzer like this:
fuzzbuild/test/fuzzing/hb-{shape,raster,vector,subset,repacker,depend}-fuzzer [-max_len=2048] [CORPUS_DIR]
Where max_len specifies the maximal length of font files to handle. The smaller the faster.
Note: The depend fuzzer requires -Ddepend_api=true meson option.
For more details consult the following locations:
Depend Closure Parity Test
The hb-depend-closure-parity test is distinct from the security fuzzers.
While security fuzzers test robustness against malformed input, the closure
parity test validates correctness by emulating the glyph closure calculation
used for subsetting with one generated from the dependency graph to avoid
implementation divergence. It should only be run on valid fonts.