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 adding ccs based on suspected regression changelists:

Add Lohit Gumurkhi, Garuda to the list of GCS synced linux fonts by drott@chromium.org - https://chromium.googlesource.com/chromium/src/+/79e55b710feeee1d464b50d5ddabb70901cbdff8

macOS V2 Sandbox: Prevent the seatbelt client writev() from blocking. by kerrnel@chromium.org - https://chromium.googlesource.com/chromium/src/+/a1bc9d0c559b92d7734e87c954cb21f3097eba14

macOS V2 Sandbox: Sandbox CDM Processes. by kerrnel@chromium.org - https://chromium.googlesource.com/chromium/src/+/e185dbf77a25908b8a2dffaeee1728ef71921369

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Those macOS Cls are macOS only. Removing myself from the CC.

This issue looks similar to  bug 755096 , hence assigning to the same owner for more updates on this issue. 

aleventhal@ Could you please take a look in to this issue?

Thanks!

ClusterFuzz has detected this issue as fixed in range 558997:559000.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900000001
Crash State:
  test_runner::WebAXObjectProxy::MisspellingAtIndex
  base::internal::Invoker<base::internal::BindState<std::__1::basic_string<char, s
  gin::internal::Dispatcher<std::__1::basic_string<char, std::__1::char_traits<cha
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=527199:527221
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=558997:559000

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

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

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