Android SurfaceViewRenderer: Never hold a pending frame indefinitely

Android SurfaceViewRenderer: Never hold a pending frame indefinitely

The original purpose with keeping one pending frame in SurfaceViewRenderer was to reduce latency for the first rendered frame when we are waiting for the Surface to be created. However, it is very dangerous to hold a pending frame indefinitely when used with a SurfaceTexture, because the SurfaceTexture only has one frame and thus holding a frame in the renderer will freeze everything and typically cause timeout crashes.

Committed: https://crrev.com/4a41361f9819b995946a87e32abe008734528cee
Cr-Commit-Position: refs/heads/master@{#10638}

[magjed_webrtc, 2015-11-13 15:25:02]

Description was changed from

==========
Android SurfaceViewRenderer: Never hold a pending frame indefinitely

The original purpose with keeping one pending frame in SurfaceViewRenderer was
to reduce latency for the first rendered frame when we are waiting for the
Surface to be created. However, it is very dangerous to hold a pending frame
indefinitely when used with a SurfaceTexture, because the SurfaceTexture only
has one frame and thus holding a frame in the renderer will freeze everything
and typically cause timeout crashes.
==========

to

==========
Android SurfaceViewRenderer: Never hold a pending frame indefinitely

The original purpose with keeping one pending frame in SurfaceViewRenderer was
to reduce latency for the first rendered frame when we are waiting for the
Surface to be created. However, it is very dangerous to hold a pending frame
indefinitely when used with a SurfaceTexture, because the SurfaceTexture only
has one frame and thus holding a frame in the renderer will freeze everything
and typically cause timeout crashes.
==========

[magjed_webrtc, 2015-11-13 15:25:02]

magjed@webrtc.org changed reviewers:
+ perkj@webrtc.org

[magjed_webrtc, 2015-11-13 15:25:09]

perkj - Please take a look.

[perkj_webrtc, 2015-11-13 15:59:30]

lgtm
thanks

[magjed_webrtc, 2015-11-13 16:20:40]

The CQ bit was checked by magjed@webrtc.org

[commit-bot: I haz the power, 2015-11-13 16:20:48]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1435413006/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1435413006/1

[commit-bot: I haz the power, 2015-11-13 16:48:07]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-13 16:48:14]

Patchset 1 (id:??) landed as
https://crrev.com/4a41361f9819b995946a87e32abe008734528cee
Cr-Commit-Position: refs/heads/master@{#10638}