Assigning to the concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: kcwu
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/08377adbc7200d4a7e0e9821cfea0809ce61cd82
Time: Thu Feb 18 19:12:42 2016
Files content_main_delegate.cc, content_main_runner.cc are changed in this cl (and is part of stack frame #1, "content::ContentMainDelegate::CreateContentGpuClient")
Minimum distance from crash line to modified line: 15. (file: content_main_runner.cc, crashed on: 254, modified: 239).

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

ClusterFuzz has detected this issue as fixed in range 484782:484819.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  content::ContentMainDelegate::CreateContentGpuClient
  content::ContentClientInitializer::Set
  content::ContentMainRunnerImpl::Initialize
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=375259:376290
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=484782:484819

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

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

I haven't investigated it yet. No idea why it was fixed.

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

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