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 adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/55d2881ba47ca3ba4eb6fe93f08ad98613777c5f (ParsedContentType parameter name matching should be case insensitive).

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.

Am on a boat @  roughly latitude 36.802197, longitude —121.785957

Reception with data and wifi usu. always bad.

1 hour into using Beta and bandwith is impressive on a Sunday!  Chrome is loading fast! Usually very congested.  Thanks guys!  Feelin' like I'm 5G!

ClusterFuzz testcase 6626894940995584 appears to be flaky, updating reproducibility label.

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "mhtml/mhtml_parser.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/ee1a7ef4d3573b44b751f51b122d2fa1eccc3caf

dewittj@ -- 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!

ClusterFuzz has detected this issue as fixed in range 621021:621022.

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

Fuzzer: libFuzzer_mhtml_parser_fuzzer
Fuzz target binary: mhtml_parser_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7fff9f070f28
Crash State:
  blink::MHTMLParser::ParseArchiveWithHeader
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=621021:621022

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

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

ClusterFuzz testcase 6626894940995584 is verified as fixed, so closing issue as verified.

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