GpuVAFactories: Initialize VEA supported profiles by cached info of GpuInfo
crrev.com/c/2035481 delays filling VEA supported profiles in GpuVideoAcceleratorFactoriesImpl because it queries GPU process the supported profiles, instead of referring cached info of GpuInfo instance. If getVEASupportedProfiles() is called in flight, the function reports as if the HW encoders support no profile. The issue due to this timing problem happens in fact on some CrOS devices. This CL mitigates the timing issue by setting the initialized VEA supported profiles to ones based on cached info of GpuInfo instance. Besides, this clarifies a caller of getVEASupportedProfiles() that the function returns nullopt if the factory hasn't got the results from GPU process. Bug: b:147404923 Test: webrtc.RTCPeerConnection.* on soraka and kukui Change-Id: Ie6867cb6f79934f66cf8550e2d41ec54671a5487 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2035461 Commit-Queue: Hirokazu Honda <hiroh@chromium.org> Reviewed-by:Dan Sanders <sandersd@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#742619}
Showing
Please register or sign in to comment