Predator and CL did not provide any possible suspects.
Using Code Search for the file, "v8_initializer.cc" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/124254af04fd234fffa434b8b4380f5056528e3b

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

Not related to https://bugs.chromium.org/p/chromium/issues/detail?id=711275. Assigning to Jochen who owns gin::V8Initializer - did anything change there?

ClusterFuzz has detected this issue as fixed in range 474949:474979.

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

Fuzzer: libfuzzer_blink_png_decoder_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900003666
Crash State:
  base::debug::DebugBreak
  gin::V8Initializer::LoadV8Natives
  content::TestBlinkWebUnitTestSupport::TestBlinkWebUnitTestSupport
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=474907:474949
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=474949:474979

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


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

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