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/+/59d9af6de66ddcbb516fa02fc6c06d58cb26ec02 (Address comments in form parsing).

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.

I am positive that this is not https://crrev.com/c/1032791.
Looking at the reported stack trace, I'm adding some relevant labels.

Looks like we got a reproducible clusterfuzz issue for a font crash, with luck this could help us track down the long open "no fallback" issue.

ClusterFuzz has detected this issue as fixed in range 573498:573499.

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

Fuzzer: inferno_canvas_wrecker
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000000
Crash State:
  blink::WebClipboardImpl::WriteImageToClipboard
  blink::WebClipboardImpl::WriteImage
  blink::Pasteboard::WriteImage
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=554669:554670
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=573498:573499

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

Additional requirements: Requires Gestures

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 5096623001305088 is verified as fixed, so closing issue as verified.

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