Author: sprang
Project: chromium-webrtc
Changelist: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+/4a86445d7005adc725b568dbfb06fc5692000222
Time: Fri Dec 02 15:29:44 2016
Lines 700-702, 737-743 of file rtcp_receiver.cc which potentially caused crash are changed in this cl (frame #4, "webrtc::RTCPReceiver::HandleXrTargetBitrate"; frame #5, "webrtc::RTCPReceiver::HandleXr").
Minimum distance from crash line to modified line: 0. (file: rtcp_receiver.cc, crashed on: 700, modified: 700).

ClusterFuzz has detected this issue as fixed in range 436613:436689.

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

Fuzzer: libfuzzer_rtcp_receiver_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e900003879
Crash State:
  rtc::FatalMessage::~FatalMessage
  webrtc::BitrateAllocation::SetBitrate
  webrtc::RTCPReceiver::HandleXrTargetBitrate
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=436245:436263
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=436613:436689

Minimized Testcase (0.71 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94Kkbo7ykwDV3CFr0ShZXjcvkVOAI-BEiMcBSX6jQXvbuELxOqeJYsiJ5I1ZnnHFmViIUuYv1z-rmMisseibRpwtiqSUrecz0f-wYvbaOQW2PLZKd16R7hGz4VmAFx_onSyiQDMTn7dJn9b3vwjB8rErcd7Lg?testcase_id=5455062265757696

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 testcase 5455062265757696 is verified as fixed, so closing issue.

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