GitLab

A recent try where we incorrectly set negative delay in
FakeAudioOutputStream revealed this. It's certainly possible that this
is happening in production with OS provided streams under odd
conditions, so clamp to zero in these cases.

R=tguilbert

Change-Id: I032bb721f339cdbe34ed513d3c40223aca66fb5d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899560
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Auto-Submit: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712766}