The result is a list of CLs that change the crashed files.

Author: stefan
Project: chromium-webrtc
Changelist: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+/48722051cea88ad1c84e1bf66031056eb71cb88d
Time: Fri Sep 02 11:07:28 2016
Lines 41-48 of file pps_parser.cc which potentially caused crash are changed in this cl (frame #2, "webrtc::PpsParser::ParsePps").

Lines 489-519, 536-539 of file rtp_format_h264.cc which potentially caused crash are changed in this cl (frame #3, "webrtc::RtpDepacketizerH264::ProcessStapAOrSingleNalu").
Minimum distance from crash line to modified line: 0. (file: pps_parser.cc, crashed on: 45, modified: 45).

--------------------------------------------------------------------

Please note that this has been found with a debug build. Let us know if we should ignore crashes like this or should disable fuzzing with Debug build for h264_depacketizer_fuzzer.

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

Fuzzer: libfuzzer_h264_depacketizer_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  Don't know how to parse CABAC streams in pps_parser.cc
  SignalHandler
  libpthread.so.0
  abort
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=416534:416553

Minimized Testcase (0.02 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96cNAht-BIu3R6B7kSGSTyS2StnySsRyET2-MaDltnWHd0tIJL8SzMT7s6pQRHPkkpaCJ1Mps5tyN3LnGE2QD2y7nfwiVEHt0AZJv_KcBiCX8zWgVwXYGEDVpwpu_Gbg50phV5j45P_fqyy1_EPFynxnmmZ2Q?testcase_id=6380724150337536

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

This was just fixed in webrtc:
https://chromium.googlesource.com/external/webrtc/+/126ee727a083fd99a2bfcc654062478dcccf3a3a

ClusterFuzz has detected this issue as fixed in range 417261:417322.

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

Fuzzer: libfuzzer_h264_depacketizer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e900001a24
Crash State:
  webrtc::PpsParser::ParseInternal
  webrtc::PpsParser::ParsePps
  webrtc::RtpDepacketizerH264::ProcessStapAOrSingleNalu
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=416523:416547
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=417261:417322

Minimized Testcase (0.02 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94ZpyKYZDXTIZemS2C4wSZDRlxPTr6pW6PlMaK9tatFFn_695lcTTUplr95TWgE1_i7mK2wDvayBaLbFUwqkGqDVgy7tOsGTOawLIi7_msLxyD8J7cAdcQSSQN-VdFwlFbNAWfAiWplTs3WU3Z3AmuBMSmvnw?testcase_id=6011238918389760

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.

ClusterFuzz has detected this issue as fixed in range 417039:417277.

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

Fuzzer: libfuzzer_h264_depacketizer_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  Don't know how to parse CABAC streams in pps_parser.cc
  SignalHandler
  libpthread.so.0
  abort
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=416534:416553
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=417039:417277

Minimized Testcase (0.02 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96cNAht-BIu3R6B7kSGSTyS2StnySsRyET2-MaDltnWHd0tIJL8SzMT7s6pQRHPkkpaCJ1Mps5tyN3LnGE2QD2y7nfwiVEHt0AZJv_KcBiCX8zWgVwXYGEDVpwpu_Gbg50phV5j45P_fqyy1_EPFynxnmmZ2Q?testcase_id=6380724150337536

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.

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