Trees in Viz: Chrome's Centralized Compositing Engine
Blink28630 Marras 2025

Trees in Viz: Chrome's Centralized Compositing Engine

The source details a significant re-architecture of the Chromium rendering pipeline, known as JellyMander, centered on the feature Trees in Viz (TiV). This change shifts the core task of frame compositing—the process of calculating layer positions and generating draw commands—from individual renderer processes to the centralized Viz service running in the GPU process. Renderers now serialize and transmit raw visual data, including their layer tree and associated property trees, which Viz uses to compute the final display frame. This centralization is designed to reduce CPU overhead in the content process, facilitate unified scheduling, and enable major performance optimizations, particularly for rendering across site-isolated frames. Although Phase 1 focused on remote compositing, future phases aim to fully relocate complex dynamic updates, such as smooth scrolling and compositor animations, into Viz. The document also highlights the use of Mojo IPC and rigorous automated testing required to synchronize state and maintain visual fidelity across this new multi-process boundary.

Jaksot(459)

[DEEP] Chromium Threaded Implementation of CSS Position Sticky

[DEEP] Chromium Threaded Implementation of CSS Position Sticky

The provided text outlines the technical architecture of how the Chromium browser handles CSS sticky positioning across its main and compositor threads. The process begins in Blink, where the main thr...

10 Maalis 37min

[PRO] Chromium Compositor Sticky: Implementation and Impl-Thread Mechanics

[PRO] Chromium Compositor Sticky: Implementation and Impl-Thread Mechanics

These sources explain how the Chromium browser engine implements sticky positioning across its main and compositor threads. The process begins in Blink, where layout geometry is calculated and cached ...

10 Maalis 50min

Blink LayoutNG: Architecture of the Physical Fragment Tree

Blink LayoutNG: Architecture of the Physical Fragment Tree

These sources describe the architectural design of the Chromium Blink layout engine, specifically focusing on how physical fragments serve as durable post-layout output. The documentation explains tha...

8 Maalis 35min

Mechanics of the Blink Pre-Paint Tree Walk

Mechanics of the Blink Pre-Paint Tree Walk

These sources describe the pre-paint lifecycle phase in the Chromium Blink rendering engine, a process primarily responsible for paint invalidation and building paint property trees. The mechanism is ...

8 Maalis 49min

Blink to CC Property Tree Conversion and Commit Pipeline

Blink to CC Property Tree Conversion and Commit Pipeline

This technical deep dive clarifies the separation of duties between Blink and the Chrome compositor (cc) regarding property tree construction. The text explains that Blink converts its own paint prope...

5 Maalis 33min

Navigating Chromium Feature Launches and W3C TAG Reviews

Navigating Chromium Feature Launches and W3C TAG Reviews

The provided text details the W3C Technical Architecture Group (TAG) review and its essential role within the Chromium feature launch process. Rather than a mere formality, this review serves as archi...

5 Maalis 46min

[ADV] Chromium InputRouterImpl Deep Dive and Architecture Analysis

[ADV] Chromium InputRouterImpl Deep Dive and Architecture Analysis

The provided text explains the InputRouterImpl, a critical browser-side component in Chromium that manages the routing of input events like mouse clicks, touch, and gestures to the renderer. This syst...

3 Maalis 32min

Chromium InputRouterImpl Deep Dive and Architecture Analysis

Chromium InputRouterImpl Deep Dive and Architecture Analysis

The provided text explains the InputRouterImpl, a critical browser-side component in Chromium that manages the routing of input events like mouse clicks, touch, and gestures to the renderer. This syst...

3 Maalis 39min