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:

Correctly serialize empty content_type for blobs. by mek@chromium.org - https://chromium.googlesource.com/chromium/src/+/bb84d169288460af40536ebbe0303cb35f11a5a1

[SPv175] Enable SlimmingPaintV175 by default by wangxianzhu@chromium.org - https://chromium.googlesource.com/chromium/src/+/0a9a5c311a1d3a298f952e495510bd6fe3faa2f6

Reland "[jumbo] avoid helper function collisions in VisibleUnits*Test.cpp" by brucedawson@chromium.org - https://chromium.googlesource.com/chromium/src/+/0fbd51f0347223bf09ae85d28fa34536c1dbb2db

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

SPv175 issue, probably duplicate of something.

CHECK failure not P1.

Similar to  bug 822817 ?

The problem is that there is a scale(0) transform on one of the elements,
leading to a non-invertible projection matrix. We should probably just
remove the DCHECK from GeometryMapper.

Removed DCHECk in https://chromium.googlesource.com/chromium/src/+/a8138ee1ae685259455fbd73b604197b55088d53

ClusterFuzz has detected this issue as fixed in range 546219:546223.

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

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

Crash Type: CHECK failure
Crash Address: 
Crash State:
  success in GeometryMapper.cpp
  blink::GeometryMapper::SourceToDestinationProjection
  blink::ChunkToLayerMapper::SwitchToChunk
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=537453:537466
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=546219:546223

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

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

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