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:

Drop UseCounter usage measurement on view-source pages. by loonybear@chromium.org - https://chromium.googlesource.com/chromium/src/+/3f921557c4cb83453bfce0fe8637e489a90064ad

Add ImageData constructor from StaticBitmapImage by zakerinasab@chromium.org - https://chromium.googlesource.com/chromium/src/+/2c863229da24ed1cb180759c9342e7a5125fd6f5

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

Gentle Ping! Could anyone let us know is there any update on this issue?

Thanks!

The CL that adds a new ImageData constructor is irrelevant to this bug, as it does not change any call site.

ClusterFuzz has detected this issue as fixed in range 569916:569917.

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

Fuzzer: attekett_dom_fuzzer
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false in SelectionAdjuster.cpp
  blink::EphemeralRangeTemplate<blink::EditingAlgorithm<blink::FlatTreeTraversal> 
  blink::SelectionTemplate<blink::EditingAlgorithm<blink::FlatTreeTraversal> > bli
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=523893:523905
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=569916:569917

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

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

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