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 Code Search for the file, "html_tree_builder.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/a464a0af1611a1c9d25253afc62238142eeb1a45

Since author is not a chromium member, assigning it to the reviewer.

tkent@ -- Could you please look into this issue.

Thanks!

This looks not a recent regression.

ClusterFuzz has detected this issue as fixed in range 576797:576798.

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

Fuzzer: inferno_twister
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false in html_tree_builder.cc
  blink::HTMLTreeBuilder::ProcessStartTag
  blink::HTMLTreeBuilder::ProcessToken
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=576797:576798

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

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

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