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 assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/bb33dbbbcf6f36daa5d7d116769b72a3c91ed9dc (Remove ScriptStreamer::resource_).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Editing command is a big source of crashing.

Crashes with CompositeEditCommand::Apply() in the stack trace should be triaged to component Blink>Editing>Command first.

Applying P3 and Available due to low usage of document.execCommand('FormatBlock')

ClusterFuzz has detected this issue as fixed in range 536251:536259.

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

Fuzzer: inferno_twister
Job Type: linux_cfi_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  chrome
  blink::Node::firstChild
  blink::Node* blink::NodeTraversal::ChildAtTemplate<blink::Node const>
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=523197:523221
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=536251:536259

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

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

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