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/+/7b4401f0ecb3645eb61c7e9f7a2b4348bfb036a2 (Add --disable-background-tasks flag.).

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.

ClusterFuzz has detected this issue as fixed in range 537942:537956.

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

Fuzzer: libFuzzer_net_data_job_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000020
Crash State:
  base::CommandLine::HasSwitch
  base::internal::GetMaxNumScheduledBackgroundSequences
  base::internal::TaskTracker::TaskTracker
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=537847:537881
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=537942:537956

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 5196870247514112 is verified as fixed, so closing issue as verified.

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