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...

Hmm, it looks identical to  issue 765940  which was automatically
closed by clusterfuzz.  So probably the test itself is flaky.

Rakina, if this is reproducing, could you work on this?

Changed to Pri-3 because this is related to DOM Mutation events.

ClusterFuzz has detected this issue as fixed in range 521421:521451.

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

Fuzzer: inferno_twister
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Null-dereference
Crash Address: 0x0000002f
Crash State:
  blink::Element::SynchronizeAttribute
  blink::Element::setAttribute
  blink::Element::SetIntegralAttribute
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=483256:483281
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=521421:521451

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

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

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