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

Author: tfarina@chromium.org
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/b8e1a10d44e6fc998e3c572868c09a097b351a59
Time: Tue Jul 24 06:08:48 2012
The CL last changed line 62 of file scoped_vector.h, which is stack frame 1.

Author: oysteine
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/a7d2d848e3522f279a87e576407a49472556f081
Time: Wed Oct 21 20:57:07 2015
The CL last changed line 264 of file background_tracing_manager_impl.cc, which is stack frame 2.

Author: tzik
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/77d41139d261342a429d2775c59d8e8a386d4c81
Time: Wed Mar 09 09:47:03 2016
The CL last changed line 389 of file callback.h, which is stack frame 3.

Author: skyostil@chromium.org
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/ad8fb459e07068582588d72fd5dabdb72e70b689
Time: Thu Aug 14 14:26:09 2014
The CL last changed line 51 of file task_annotator.cc, which is stack frame 4.

Author: caseq
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/596ad0cca35be6b20afba297d3e8c26ae52e3ec2
Time: Thu Jul 16 19:13:21 2015
The CL last changed line 493 of file message_loop.cc, which is stack frame 5.

Author: ajwong@chromium.org
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/b224f79da757434cee55b721806ff8553fc80b0a
Time: Wed Apr 20 16:02:23 2011
The CL last changed line 502 of file message_loop.cc, which is stack frame 6.

Suspected Project: chromium

Possible suspect : https://chromium.googlesource.com/chromium/src//+/a7d2d848e3522f279a87e576407a49472556f081

Please reassign if this is not related to your change.

ClusterFuzz has detected this issue as fixed in range 410634:410757.

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

Fuzzer: ipc_fuzzer_gen
Job Type: linux_asan_chrome_ipc
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000010
Crash State:
  content::BackgroundTracingManagerImpl::OnHistogramTrigger
  base::debug::TaskAnnotator::RunTask
  base::MessageLoop::RunTask
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_ipc&range=381471:381519
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_ipc&range=410634:410757

Minimized Testcase (27.39 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97tbf9SE_erYy16Y9s0yWf_Uf8oonK00runQ5EI_6kydGMnd4ezX2q9cOGMC9VihhmqwWnpYf8IOezJDkJF_9hKGDWgr1R12xL3e_D9mbgsIC2GFSnHqgtVenLcV8kNkbpApnIAGiOdY-z0IFUtdK-GjfbZbKaO4fWFNG9vhX0X0eJo0Tc?testcase_id=6414511146008576

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