From findit tool:

Author: Erik Språng
Project: chromium-webrtc
Changelist: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+/489fd97414f5ee8e1f0a7e0248e743bb06d6b2a9
Time: Thu Sep 24 13:06:57 2015
The CL last changed line 1244 of file rtcp_utility.cc, which is stack frame 5.

Author: Erik Språng
Project: chromium-webrtc
Changelist: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+/489fd97414f5ee8e1f0a7e0248e743bb06d6b2a9
Time: Thu Sep 24 13:06:57 2015
The CL last changed line 236 of file rtcp_utility.cc, which is stack frame 6.

Suspected Project: chromium-webrtc
Suspected Component: Blink>Webrtc

ClusterFuzz has detected this issue as fixed in range 408933:408943.

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

Fuzzer: libfuzzer_rtcp_receiver_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e900004826
Crash State:
  webrtc::rtcp::DecodeSymbol
  webrtc::rtcp::TwoBitVectorChunk::ParseFrom
  webrtc::rtcp::TransportFeedback::ParseChunk
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=408895:408933
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=408933:408943

Minimized Testcase (0.02 Kb): https://cluster-fuzz.appspot.com/download/AMIfv960zDBy5H1aIFUaDNdTbRyEjUFyURYkM2LzzM3vugVzvNVhvHgyp7Q-NCylxwBe0pWYzg3WUGdEGYMZNV78sHf0yELOkwVa4t67n5RczcKEG5lZm99-jWQgtraxceQKV2yWKUsZvUG2rrmHAZKazHZpm23KXA?testcase_id=6212880917856256

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

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

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