No CL in the regression range changes the crashed files. The result is the blame information.

Author: haraken@chromium.org
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/a42c8dd440be01594924581844c3b4588552d702
Time: Tue Aug 25 08:08:47 2015
The CL last changed line 845 of file HeapPage.h, which is stack frame 0.

Author: sigbjornf
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/3e5bcb132b1af136ba6faa1c152dcba2c298549f
Time: Mon May 23 14:28:16 2016
The CL last changed line 146 of file Member.h, which is stack frame 1.

Author: sigbjornf
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/3e5bcb132b1af136ba6faa1c152dcba2c298549f
Time: Mon May 23 14:28:16 2016
The CL last changed line 35 of file Member.h, which is stack frame 2.

Author: pfeldman
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/1dc6dbe22945058cf5cee6ace9c9377732476daf
Time: Tue Jun 07 15:21:59 2016
The CL last changed line 132 of file InspectorInstrumentation.cpp, which is stack frame 5.

Author: dgozman
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/6b2cf8c879c7ae20b71620dee7767b723fab3f6f
Time: Mon Apr 25 22:29:43 2016
The CL last changed line 1707 of file Document.cpp, which is stack frame 6.

Suspected Project: chromium-blink
Suspected Component: Blink>MemoryAllocator
=======================
From the above CL the changes made to the file "Member.h" from frame 1 and 2 are more realted to it.

Assigning this to reviwer of the CL

haraken@ Could you please help us in assigning this to an appropriate owner 

Thanks,

ClusterFuzz has detected this issue as fixed in range 408294:408327.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4826119547387904

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  libpepflashplayer.so
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=338452:338454
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=408294:408327

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95aEIUCi8TewVKnm0imSa4Xnlo0n3Di9JcuvyTUpVVhfHVWxOncdG7QGhEO3oaOL5M-BOceHhg9eBpaQzdF0uVB5SblbiUtlNRL8ZVkukZnNZJvBWF_Ao7ysD1YYxckRDtv5LxSc-Q1jpzMUiPIPy8WbLJU9WNTN8P1FdwF0WGttEWSykI?testcase_id=4826119547387904


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.

ClusterFuzz testcase is verified as fixed, closing issue.

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

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot