commit 81e25a95f6e2133ef999805c0a1556cf696a8015
author Vasiliy Telezhnikov <vasilyt@chromium.org> Fri Jan 31 18:18:51 2025
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Fri Jan 31 18:18:51 2025
tree 3ffe490a0038a8bb0d5b4a9f643327dba3910d66
parent 124f40b2359af6a580e20cf54cc0c6732e428d87

Don't keep reference to the AImage that is not being rendered.

AImageReader has a strict limit on the amount of images we can keep
around. Normally we set limit to 3 and there are exactly 3 references
that we hold:
* For visible image in SurfaceFlinger
* For pending SurfaceControl transaction to replace visible one
* For prepared transaction that we will submit next frame (as we're
  triple buffering).

ImageReader has its own `current_image_ref`, but normally it matches
the same image as in prepared transaction.

But in some cases early rendering mechanism can trigger rendering a
frame that later is not going to be displayed. In this case
current_image_ref transiently doesn't match any image on the rendering
path, this causes problem, because the image we're going to display
can't be acquired because we're at the limit.

This CL discards images that we're not planning on displaying.

Bug: 40856345
Change-Id: I09c1fe596690f3c7d344a7a23303224e08e737ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6219626
Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1414240}