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, "task_queue_impl.cc" suspecting the below Cl might have caused this issue

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

kraynov@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

altimin@ Could you please look into this issue.

ClusterFuzz has detected this issue as fixed in range 604863:604864.

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

Fuzzer: puzzor
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  MakeRefCounted<base::sequence_manager::internal::TaskQueueTaskRunner,
  base::sequence_manager::internal::TaskQueueImpl::CreateTaskRunner
  base::sequence_manager::TaskQueue::CreateTaskRunner
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=552470:552473
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=604863:604864

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

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

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