Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(138)

Issue 2626443003: Improve MediaPlayerBridge seek resiliance (Closed)

Created:
3 years, 11 months ago by tguilbert
Modified:
3 years, 11 months ago
CC:
chromium-reviews, jam, darin-cc_chromium.org, avayvod+watch_chromium.org, mlamouri+watch-media_chromium.org, feature-media-reviews_chromium.org
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Improve MediaPlayerBridge seek resiliance crbug.com/677280 manifested whenever we tried seeking on a non-seekable live stream, causing the MediaPlayer to crash, and the stream to never start. Dropping seeks based off of unknown or infinite media duration (for livestreams) introduced crbug.com/679482. When we resume a tab, the MediaPlayerRenderer is re-created, and if the preliminary attempt to extract the media's metadata failed, we drop the first seek. This causes the media restart after every tab switch. It turns out that there is a better fix for 677280, which prevents 679482 entirely. Currently, in MediaPlayerBridge::OnMediaPrepared(), we complete pending seeks before updating allowable operations. Updating allowable operations as a first action properly sets "CanSeekForward" and "CanSeekBackards", which then aborts any invalid seek attempts without any additional logic. BUG=679482, 677280 TEST= Manual test on a live HLS stream and non live HLS video.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+3 lines, -6 lines) Patch
M content/browser/media/android/media_player_renderer.cc View 1 chunk +1 line, -5 lines 0 comments Download
M media/base/android/media_player_bridge.cc View 2 chunks +2 lines, -1 line 0 comments Download

Messages

Total messages: 10 (5 generated)
tguilbert
PTAL. This is a follow-up/correction to yesterday's CL.
3 years, 11 months ago (2017-01-09 23:21:07 UTC) #2
sandersd (OOO until July 31)
lgtm
3 years, 11 months ago (2017-01-09 23:34:35 UTC) #3
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2626443003/1
3 years, 11 months ago (2017-01-09 23:36:22 UTC) #5
commit-bot: I haz the power
Prior attempt to commit was detected, but we were not able to check whether the ...
3 years, 11 months ago (2017-01-10 01:40:40 UTC) #8
tguilbert
3 years, 11 months ago (2017-01-10 19:06:31 UTC) #9
On 2017/01/10 01:40:40, commit-bot: I haz the power wrote:
> Prior attempt to commit was detected, but we were not able to check whether
the
> issue was successfully committed. Please check Git history manually and
re-check
> CQ or close this issue as needed.

This was committed successfully as 0d32da520686f09a43107b63e9ab365fa5af580f.
Closing this issue.

Powered by Google App Engine
This is Rietveld 408576698