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

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

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "string_piece.h" and observed some recent changes for the below file.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/e5a6dfada32caaccc93e4f3ca4cb0bd0f6cdd019%5E%21/base/strings/string_piece.h

palmer@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

This might or might not be a duplicate of the other one.

ClusterFuzz has detected this issue as fixed in range 542429:542430.

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

Fuzzer: libFuzzer_signed_exchange_header_parser_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  0UL != length_ in string_piece.h
  base::BasicStringPiece<>::front
  content::StructuredHeaderParser::ReadString
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=541008:541022
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=542429:542430

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

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.