Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/f3322d752f4eb6326b194a5f9f378f9fe9a422ee (Hardening and cleanup of base::JSONParser.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

I am fixing the crash type, this should have been marked as check failure, same as 825067. this is an issue with msan sigabrt + check failure assert.

ClusterFuzz has detected this issue as fixed in range 545931:545973.

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

Fuzzer: libFuzzer_base_json_reader_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  i < length_ in string_piece.h
  base::BasicStringPiece<std::__1::basic_string<char, std::__1::char_traits<char>,
  base::internal::JSONParser::ConsumeStringRaw
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=545272:545276
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=545931:545973

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

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