MSE: Allow range merge in specific estimated buffer duration scenarios
If a range B starts with the same timestamp as the end of the previous range A, these would normally merge due to being adjacent within the fudge room based on the end timestamp of range A (not the buffered end timestamp of A). This is sufficient for coalescing adjacent ranges in all cases except where fudge room has not been increased to account for an increased estimated buffer's duration. In complex overlap/abutting append scenarios, A and B previously would have remained outside of fudge room of each other and not have been coalesced, if A ended with an estimated duration buffer longer than the fudge room. This change patches CanAppendBuffersToEnd to recognize this specific scenario and allow A and B to coalesce. BUG=806181 TEST=CF case no longer repros locally, new SBSTest.MergeAllowedIfRangeEndTimeWithEstimatedDurationMatchesNextRangeStart 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: Ic749c2e4e0bb6cc1b69983efd16ef6e346410c9e Reviewed-on: https://chromium-review.googlesource.com/898604 Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org> Reviewed-by:Chrome Cunningham <chcunningham@chromium.org> Cr-Commit-Position: refs/heads/master@{#534871}
Showing
Please register or sign in to comment