media: Make sure we transition back to a non-loading state

media: Make sure we transition back to a non-loading state

An earilier bug-workaround kept the media in a loading state when
a read operation was pending, but didn't always transition back to
idle when the read operation was done. This CL fixes the problem
by making sure that we check the loading state after read callbacks.

These extra calls to check the loading state can in some cases cause
us to miss progress callbacks. We fix this by allowing in-flight
progress callbacks to complete even if reader_ has been destroyed.

BUG=662615
Review-Url: https://codereview.chromium.org/2481673004
Cr-Commit-Position: refs/heads/master@{#430860}
(cherry picked from commit a89cc8bcb5d204e3f42eb56d2db24837ba0d3a8a)

Committed: https://chromium.googlesource.com/chromium/src/+/726c376476785452c478c4bc928c12c1eb62e35d

[hubbe, 2016-11-10 18:36:26]

Description was changed from

==========
media: Make sure we transition back to a non-loading state

An earilier bug-workaround kept the media in a loading state when
a read operation was pending, but didn't always transition back to
idle when the read operation was done. This CL fixes the problem
by making sure that we check the loading state after read callbacks.

These extra calls to check the loading state can in some cases cause
us to miss progress callbacks. We fix this by allowing in-flight
progress callbacks to complete even if reader_ has been destroyed.

BUG=662615

Review-Url: https://codereview.chromium.org/2481673004
Cr-Commit-Position: refs/heads/master@{#430860}
(cherry picked from commit a89cc8bcb5d204e3f42eb56d2db24837ba0d3a8a)
==========

to

==========
media: Make sure we transition back to a non-loading state

An earilier bug-workaround kept the media in a loading state when
a read operation was pending, but didn't always transition back to
idle when the read operation was done. This CL fixes the problem
by making sure that we check the loading state after read callbacks.

These extra calls to check the loading state can in some cases cause
us to miss progress callbacks. We fix this by allowing in-flight
progress callbacks to complete even if reader_ has been destroyed.

BUG=662615

Review-Url: https://codereview.chromium.org/2481673004
Cr-Commit-Position: refs/heads/master@{#430860}
(cherry picked from commit a89cc8bcb5d204e3f42eb56d2db24837ba0d3a8a)

Committed:
https://chromium.googlesource.com/chromium/src/+/726c376476785452c478c4bc928c...
==========

[hubbe, 2016-11-10 18:36:27]

Committed patchset #1 (id:1) manually as
726c376476785452c478c4bc928c12c1eb62e35d.