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 the code search for the file, “partition_alloc.h” assigning to concern owner.

Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/f48b1f3e72ee8a726422dbc3fb9d0d47b251a6b8

ajwong@ -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.


Thank You...

ClusterFuzz has detected this issue as fixed in range 520264:520300.

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

Fuzzer: libFuzzer_renderer_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  Alloc
  BufferMalloc
  blink::HTMLDocumentParser::NotifyPendingTokenizedChunks
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=519646:519660
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=520264:520300

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

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

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