The Tiered Compilation System
To execute complex WebAssembly (Wasm) applications at near-native speeds, Google Chrome utilizes a sophisticated, multi-tiered compilation strategy. When a Wasm app first loads, Chrome immediately throws it at a “Baseline Compiler” (Liftoff), which translates the code incredibly fast so the application can start instantly, even if the resulting execution isn’t perfectly optimized. Simultaneously in the background, a much slower but highly optimized compiler (TurboFan) begins analyzing the same code. Once TurboFan finishes its deep optimization, Chrome dynamically hot-swaps the running code, “tiering up” from the baseline version to the highly optimized version. The “Enable WebAssembly Tiering” flag controls this dynamic hot-swapping mechanism.
While tiering is the secret sauce that makes heavy browser apps feel both responsive on startup and fast during sustained use, it introduces immense complexity. The browser must seamlessly manage memory and execution state while swapping engines mid-flight. For developers debugging specific WebAssembly memory leaks, profiling raw execution speeds, or analyzing deterministic behavior, this dynamic swapping makes it impossible to isolate which compiler is causing an issue. In these strict debugging scenarios, developers often need to disable tiering to force Chrome to stick to a single compilation strategy throughout the entire lifecycle of the application.
How to Turn Off Wasm Tiering
You can force Chrome to disable dynamic compiler swapping via the experimental flags menu.
- Open Google Chrome.
- Click inside the main address bar at the top of the browser window.
- Type
chrome://flagsand press Enter. - On the “Experiments” page, use the search bar to look for Enable WebAssembly Tiering.
- If the flag is available, click the dropdown menu next to it and change it from “Default” (or Enabled) to Disabled.
- Click the blue Relaunch button at the bottom of the screen.
Upon restarting, Chrome will no longer hot-swap WebAssembly execution engines. The application will run entirely on the initial compilation tier, which may impact sustained performance but guarantees consistent execution logic for debugging purposes.