Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/0903fe19af33f53932430736caaee9fcfb248968 (Import wpt@43dd25c888da9b903cedeb3bb5b8a832b2d51b97).

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.

Not a security issue and no reports in the wild, lowering priority.

Probably identical to the not reproducible  issue 820821 .

ClusterFuzz has detected this issue as fixed in range 556337:556338.

Detailed report: https://clusterfuzz.com/testcase?key=5155911568719872

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::OpenTypeVerticalData::GetVerticalTranslationsForGlyphs
  blink::HarfBuzzGetGlyphVerticalOrigin
  hb_font_t::get_glyph_v_origin_with_fallback
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=554670:554671
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=556337:556338

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5155911568719872

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5155911568719872 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.