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/+/533b299c8b27b6f00387f2c3dfb018c175868271 (v4l2_vda: Adjust the (D)VLOG levels and change some DVLOGs to VLOGs and LOG(ERROR) to VLOG(1)).

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 mentioned change makes a difference only on ChromeOS.
Additionally, the CL only changes the log message levels.
Therefore, I don't think this CL increase a memory leakage on Linux.
If my opinion is incorrect, please reassign me.

Thanks

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "PartitionAllocator.cpp" and observed there was some recent changes for the below file.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/6e19c2610f76d08d8d45d104740c0512587a54aa

keishi@ -- 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!

ClusterFuzz has detected this issue as fixed in range 533163:533171.

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

Fuzzer: libFuzzer_renderer_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=526187:526188
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=533163:533171

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

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

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