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 adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/7d3def8575ecd2e5e2e7ab7f585961206007bd25 (Adds LPM-based SQLite fuzzer).

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.

I think there is a solid chance this leak is in our patches.

ClusterFuzz has detected this issue as fixed in range 618098:618104.

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

Fuzzer: libFuzzer_sqlite3_fts3_lpm_fuzzer
Fuzz target binary: sqlite3_fts3_lpm_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  sqlite3MemMalloc
  sqlite3Malloc
  memjrnlWrite
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=615335:615343
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=618098:618104

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 4680026404159488 is verified as fixed, so closing issue as verified.

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