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

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

Predator and CL could not provide any possible suspects.

Using the code search for the file, “Element.cpp & ContainerNode.cpp”  assigning to concern owner because of his recent work on suspect CL.
Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/be39eca66962913558c32b74c52da41ef91386b0

nainar@ - Could you please look into this issue and kindly reassign if it has nothing to do with the above changes.

Thank You.

This crashes without my CL and crashes in M63 as well. 

ClusterFuzz has detected this issue as fixed in range 549059:549062.

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

Fuzzer: inferno_twister
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::FirstLetterPseudoElement::AttachFirstLetterTextLayoutObjects
  blink::Element::RebuildLayoutTree
  blink::Element::RebuildLayoutTree
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=508795:508862
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=549059:549062

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

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

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