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

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

As per the  Issue 870680  owner assigning this issue to @wangxianzhu.
@wangxianzhu -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thanks.

This is a known issue that happens in real world very rarely.

ClusterFuzz has detected this issue as fixed in range 589046:589065.

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

Fuzzer: marty_html_twiddler
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  state_stack_.size() && state_stack_.back().type == StateEntry::kClip. Error: Chu
  blink::ConversionContext::SwitchToClip
  blink::ConversionContext::SwitchToChunkState
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=543289:543293
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=589046:589065

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

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

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