The Memory-Hungry Rasterization
Google Chrome constantly experiments with ways to render web pages faster. One such experimental feature is the “Zero-Copy Rasterizer.” When a web page is drawn, the browser must convert HTML and CSS code into pixels (rasterization). Traditionally, this rasterized image is stored in main system memory and then copied over to the GPU’s memory to be displayed. Zero-copy rasterization attempts to write this data directly into the GPU memory, skipping the system RAM entirely.
On high-end systems with modern GPUs, this drastically reduces memory bandwidth overhead and improves scrolling performance. However, on systems with integrated graphics, older discrete GPUs, or limited Video RAM (VRAM), forcing zero-copy rasterization can cause significant instability. If you are experiencing Chrome tabs crashing with “Out of Memory” errors, severe visual artifacting (like black checkerboards when scrolling), or browser freezes during video playback, this experimental flag may be overwhelming your GPU. Disabling it forces Chrome to use the slower, but significantly more stable, traditional memory copying method.
How to Disable the Zero-Copy Rasterizer
You must dive into Chrome’s experimental flags menu to change how pages are drawn.
- Open Google Chrome.
- Click inside the main address bar at the top of the browser.
- Type
chrome://flagsand press Enter. - A page titled “Experiments” will load.
- In the search bar at the top, type Zero-copy rasterizer.
- The specific flag will appear highlighted in yellow. Next to it is a dropdown menu.
- Click the dropdown menu and select Disabled.
- Chrome will prompt you to restart the browser. Click the blue Relaunch button.
Upon restarting, Chrome will abandon direct-to-GPU writing. Your browsing might be fractionally slower to render complex pages, but visual stability and tab reliability on older hardware will drastically improve.