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/+/6bdfed7585104a47ff5aefe81bbc49d4ef5bb8b4 (Support for Autofill in VR).

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.

The changelist that is mentioned here is landed on April 5 (67), and only has effect on Android. The bug is for Linux and is impacting Stable 65.0.3325.181, Beta 66.0.3359.81.
This issue doesn't seems to be related to the particular changelist that is mentioned.

This crash occurs very frequently on linux platform and is likely preventing the fuzzer attekett_dom_fuzzer from making much progress. Fixing this will allow more bugs to be found.

Marking this bug as a blocker for next Beta release.

If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.

Hi, this should be caused by a finch experiment, but the last time I checked it was disabled. Looking into it now.

ClusterFuzz has detected this issue as fixed in range 552642:552643.

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

Fuzzer: attekett_dom_fuzzer
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  ObtainAndSetContextProvider
  Invoke<base::OnceCallback<void
  MakeItSo<void
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=548273:548274
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=552642:552643

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

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

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