CHECK failure: slice.num_characters in harfbuzz_shaper.cc |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5756367197175808 Fuzzer: libFuzzer_blink_harfbuzz_shaper_fuzzer Fuzz target binary: blink_harfbuzz_shaper_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: slice.num_characters in harfbuzz_shaper.cc blink::QueueCharacters blink::HarfBuzzShaper::ExtractShapeResults Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514696:514717 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5756367197175808 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Jan 16
(6 days ago)
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Jan 16
(6 days ago)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/befb16634bb440cf5442979ad262832b4cebd43e (Update ICU to version 60.1 + local patches). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Jan 16
(6 days ago)
This looks like issue 881447 and may be caused by some ClusterFuzz flakiness? I would suggest to look at the crash timeline in the detailed report and see if it persists over several days. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Jan 16 (6 days ago)Labels: Test-Predator-Auto-Components