Assigning to concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: avayvod
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/c4bfb0e6139a447f0b4eeb31d34064b7ebf0fdcc
Time: Fri Jan 13 01:07:01 2017
Files decoder_stream.cc, decoder_stream_traits.cc are changed in this cl (and is part of stack frame #2, "media::DecoderStream<"; frame #3, "media::DecoderStream<")
Minimum distance from crash line to modified line: 9. (file: decoder_stream_traits.cc, crashed on: 173, modified: 164).

@avayvod -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 501012:501053.

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

Fuzzer: ochang_search_index_mutator
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  media::MovingAverage::AddSample
  media::DecoderStreamTraits<
  media::DecoderStream<
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=443393:443475
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=501012:501053

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

See https://github.com/google/clusterfuzz-tools 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 5094140397486080 is verified as fixed, so closing issue as verified.

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