Predator could not provide any possible suspects.
Assigning to the concern owner from CL --
https://chromium.googlesource.com/chromium/src/+log/64851d6549e974416f48bf85a95621076393ae16..9839ce4e4a0db225f4fc728ccae96a7e40757482?pretty=fuller&n=10000

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

@tobiasjs -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

The following revision refers to this bug:
  https://chromium.googlesource.com/breakpad/breakpad/+/c4335f04356afe67cabc4cf5eb3d1f16294c3a03

commit c4335f04356afe67cabc4cf5eb3d1f16294c3a03
Author: Tobias Sargeant <tobiasjs@google.com>
Date: Wed Aug 30 17:28:54 2017

Fix memory leak in ppc64 stackwalker

BUG= 757166 

Change-Id: I967a6903332b9c3d16b583f7fa4d3c9c44c2f729
Reviewed-on: https://chromium-review.googlesource.com/643267
Reviewed-by: Leonard Mosescu <mosescu@chromium.org>

[modify] https://crrev.com/c4335f04356afe67cabc4cf5eb3d1f16294c3a03/src/processor/stackwalker_ppc64.cc

ClusterFuzz has detected this issue as fixed in range 499613:499635.

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

Fuzzer: libFuzzer_minidump_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  google_breakpad::StackwalkerPPC64::GetCallerFrame
  google_breakpad::Stackwalker::Walk
  google_breakpad::MinidumpProcessor::Process
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=494860:494945
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=499613:499635

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

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

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