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

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

Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.
Thank You.

yosin@, could you take a look?

Lower to Pri-3 since real world usage of formatBlock command with unusual HTML is low.

ClusterFuzz has detected this issue as fixed in range 525936:525937.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000030
Crash State:
  nextSibling
  NextSkippingChildren
  blink::CompositeEditCommand::CloneParagraphUnderNewElement
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=297214:297254
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=525936:525937

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

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

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