SUSPECTED CHANGELISTS IN CHROMIUM:
===================================
Git blame below is NOT necessarily who introduced the crash nor the owner for it. Please check the code before assigning to anyone.(No CL in the regression range changed the crashing files.) 

Author: mostynb@opera.com
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/901a5e3835718e8872f38af32d65fce7ea3fcbeb
Time: Mon Apr 08 23:26:25 2013
The CL last changed line 221 of file debugger_posix.cc, which is stack frame 2. 

Author: brettw@chromium.org
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/58580359a452cb7c3b9580edc0843c3ab3d158df
Time: Tue Oct 26 04:07:50 2010
The CL last changed line 251 of file debugger_posix.cc, which is stack frame 3. 

Author: rch@chromium.org
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/82d89abc03ea6fd6b9258f0e57be0290b33d7eb1
Time: Fri Feb 28 18:25:34 2014
The CL last changed line 748 of file logging.cc, which is stack frame 4. 

Author: aizatsky
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/022c9c2dd56926d03f2dd21036ebde0da869ee7b
Time: Mon Oct 31 21:42:21 2016
The CL last changed line 51 of file correctness_fuzzer.cc, which is stack frame 5.

From the above CL list suspecting the below based on the recent changes made to file "correctness_fuzzer.cc".
Suspect : https://codereview.chromium.org/2449323004
aizatsky@ : Could you please take a look into this if it is related to your change.

Currently its impacting to head.

durga.behera@, FYI, aizatsky@ is an author of the fuzzer.

danakj@, since you've reviewed the fuzzer, I hope that you can help to find an owner. Could you please help?

The problem seems to be in handling of \u0000 value in the input string.

 Issue 661919  has been merged into this issue.

aizatsky something you can look at?

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

ClusterFuzz testcase 5368468754137088 is flaky and no longer reproduces, so closing issue.

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

ClusterFuzz has detected this issue as fixed in range 455091:455226.

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

Fuzzer: libfuzzer_base_json_correctness_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  parsed_output == double_parsed_output. Parser/Writer mismatch.
  base::debug::DebugBreak
  _start
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=428776:428837
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=455091:455226

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95tTCqO15VH4f4k-zfSD6_aRELsR0dnlCKEeUyEATE8osUN28Y82r5hBr6VqSrsjyJ8rhuFarU9ZcAo6SRTFT-9C3qOoHXuaiXt6dbUmMezAkiWGZwIU5tavn5JyjZ9RmVA6XLXaCktK1LUtRnlI9pPuSd5wii14IQX3jE6frcXPG9iHIK4e-y0AMSdsKHKRkU1cM-Rw14bWnma8l8sVsMff-BUURsVnIyTAQ_LOletvwjLqf7lGbu9mfyuIIxZQ6XmU6tP2M31L-2Ms5_YZUq9rPJ0zMS9QX-TWfnAJS2VnCwn7boD8f7du0-wDEb8JlEciX03of_z8e4Rht3r8969sLFLisXyx6NrzjVPMmG69dzPhjQ?testcase_id=5241221036638208


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.