
Sign up to save your podcasts
Or


In Chrome’s rendering pipeline, the Viz service in the GPU process owns a viz::Display object. A Display is responsible for taking aggregated CompositorFrames (produced by the SurfaceAggregator), drawing them using the appropriate renderer (Skia or software) and swapping the resulting buffer to the physical output surface. The method Display::DrawAndSwap(const DrawAndSwapParams& params) performs this work. The display scheduler calls DrawAndSwap for every frame it wants to display. On some platforms such as Lacros, DrawAndSwap uses the root surface size as the display’s size; the note on display size explains that display_->Resize sets current_surface_size_, and DrawAndSwap uses this value to determine whether the current frame needs a resize.
By Free DebreuilIn Chrome’s rendering pipeline, the Viz service in the GPU process owns a viz::Display object. A Display is responsible for taking aggregated CompositorFrames (produced by the SurfaceAggregator), drawing them using the appropriate renderer (Skia or software) and swapping the resulting buffer to the physical output surface. The method Display::DrawAndSwap(const DrawAndSwapParams& params) performs this work. The display scheduler calls DrawAndSwap for every frame it wants to display. On some platforms such as Lacros, DrawAndSwap uses the root surface size as the display’s size; the note on display size explains that display_->Resize sets current_surface_size_, and DrawAndSwap uses this value to determine whether the current frame needs a resize.