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

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

vmpstr@, looks like another clip stack bug, although I'm guessing it's the same underlying cause as the previous one.

Feel free to pass it on. CHECK failures can wait on wangxianzhu@.

Yeah this looks like the same issue as before. ( crbug.com/869264 ) That bug is for some reason detected as fixed but afaik no changes have happened. The context of my investigation is on that bug. 

ClusterFuzz has detected this issue as fixed in range 584667:584668.

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

Fuzzer: ifratric-browserfuzzer-v3
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::StartEffect
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=543289:543291
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=584667:584668

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

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

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