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 assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/c4c936cf14b8c7f125a6087241b7b7983644ee49 (MSE: Signal SBS of new CFG more granularly when buffering ByPts).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

I have a local repro. Also, this repro no longer occurs with the fix for  bug 803018  (https://chromium-review.googlesource.com/c/chromium/src/+/871517 patch set 4) applied locally, and investigation of the successful repro without that change indicates that the fault in MergeAllAdjacentRanges (fixed in https://chromium-review.googlesource.com/c/chromium/src/+/871517) is what led to this bug.

Not marking duplicate, since I think that might prevent clusterfuzz verification. I'll block this bug though on  bug 803018 .

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ef5f357c1f1375f3167bc1d9ecc9b5188ad421f6

commit ef5f357c1f1375f3167bc1d9ecc9b5188ad421f6
Author: Matt Wolenetz <wolenetz@chromium.org>
Date: Mon Jan 22 21:13:14 2018

MSE: Fix a couple fudge room usage faults

When fudge room increases, MergeAllAdjacentRanges should merge all
ranges that are adjacent based on the new fudge room. Previous code
would not try to merge sets of more than 2 adjacent ranges, resulting in
disjoint ranges which should have been coalesced. This change updates
MergeAllAdjacentRanges to try to merge the current range with the next
one repeatedly if the previous merge was successful.

This change also stops using the approximate buffer duration (based on
the maximum duration or continuous interbuffer DTS distance seen so far)
as the reported range end time for ranges ending with a zero duration
buffer. In combination with the previously broken MergeAllAdjacentRanges
logic, approximated range end times that grow dynamically as a side
effect of fudge room growth led to previously disjoint ranges
overlapping each other (and failing the strengthened IsRangeListSorted()
debug build verifications added as part of fixing  bug 791095 .)

This change uses a constant 1 microsecond for the duration of a buffer
that is reported as zero duration by the stream parsing and frame
processor when calculating the buffered end time of a range.

Since public base::TimeDelta::FromInternalValue usage is deprecated,
this change also switches usage to FromMicroseconds in SBS and SBR.

BUG= 803018 , 803293 , 791095 
TEST=SBS.*ZeroDurationBuffersThenIncreasingFudgeRoom, and removal of a
FrameProcessorTest that verified the obsolete fudge-room-based buffered
range reporting. The clusterfuzz cases in bugs  803018  and  803293  also
no longer repro locally with this change.

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I8b4adfeb5064c15e57211d2f07132e7723f7f66a
Reviewed-on: https://chromium-review.googlesource.com/871517
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Cr-Commit-Position: refs/heads/master@{#530992}
[modify] https://crrev.com/ef5f357c1f1375f3167bc1d9ecc9b5188ad421f6/media/filters/frame_processor_unittest.cc
[modify] https://crrev.com/ef5f357c1f1375f3167bc1d9ecc9b5188ad421f6/media/filters/source_buffer_range_by_dts.cc
[modify] https://crrev.com/ef5f357c1f1375f3167bc1d9ecc9b5188ad421f6/media/filters/source_buffer_range_by_pts.cc
[modify] https://crrev.com/ef5f357c1f1375f3167bc1d9ecc9b5188ad421f6/media/filters/source_buffer_stream.cc
[modify] https://crrev.com/ef5f357c1f1375f3167bc1d9ecc9b5188ad421f6/media/filters/source_buffer_stream.h
[modify] https://crrev.com/ef5f357c1f1375f3167bc1d9ecc9b5188ad421f6/media/filters/source_buffer_stream_unittest.cc

Pending CF verification, I believe this is fixed by #4.

ClusterFuzz has detected this issue as fixed in range 530991:530997.

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

Fuzzer: libFuzzer_mediasource_WEBM_OPUS_VP9_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  last_range == range_for_next_append_ in source_buffer_stream.cc
  media::SourceBufferStream<media::SourceBufferRangeByPts>::OnStartOfCodedFrameGro
  media::SourceBufferStream<media::SourceBufferRangeByPts>::OnStartOfCodedFrameGro
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=521932:521962
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=530991:530997

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.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 5256529875042304 is verified as fixed, so closing issue as verified.

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