media::V4L2VideoDecoder: introduce kMaxNumOfInstances
MS Teams on ARM-based ChromeOS with the new VideoDecoder (not launched) tries to create many direct video decoders (I see e.g. 42 on kukui); some succeed but eventually they don't and the tab ends up hitting an OOM. The process is not well understood and needs further debugging. This CL replicates the kMaxNumOfInstances [1] logic from the legacy VideoDecodeAccelerator to the new direct VideoDecoder, so the new behaves like the old, allowing us to unblock the linked bug. [1] https://source.chromium.org/search?q=kMaxNumOfInstances&sq=&ss=chromium%2Fchromium%2Fsrc:media%2Fgpu%2Fv4l2%2F Landing this provision on Kukui was already discussed on . https: //chromium-review.googlesource.com/c/chromium/src/+/2372926/10#message-ca9039b5fb3eb9e1fbcd9701ddc476b257f088d6 Bug: b/170870476 Change-Id: Ice0d9f16e7ca0063c03cccdafe54e29ad5602cd0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628069 Commit-Queue: Miguel Casas <mcasas@chromium.org> Reviewed-by:Andres Calderon Jaramillo <andrescj@chromium.org> Reviewed-by:
Fritz Koenig <frkoenig@chromium.org> Cr-Commit-Position: refs/heads/master@{#843377}
Showing
Please register or sign in to comment