Why does this happen with Google Maps?

Google Maps uses WebGL for 3D rendering. GPU resource pressure from other tabs or driver issues can cause the Maps WebGL context to be lost.

Is this a hardware problem?

Usually not. It is most often a driver issue or resource exhaustion. Update GPU drivers and reduce the number of WebGL-using tabs.

Browser WebGL Context Lost — GPU Rendering Failure in Browser

Warningweb development

Overview

Fix WebGL context lost errors causing 3D graphics, games, and maps to stop rendering, usually caused by GPU driver crashes, resource limits, or memory pressure.

Key Details

WebGL provides GPU-accelerated 3D rendering in the browser via the HTML5 canvas element
Context lost (CONTEXT_LOST_WEBGL) means the GPU or driver dropped the WebGL rendering context
The browser may kill a WebGL context to reclaim GPU memory for other tabs or the OS
GPU driver crashes (TDR on Windows) force all WebGL contexts to be lost
Applications can handle context loss by listening for the webglcontextlost event

Common Causes

GPU driver crash or Timeout Detection and Recovery (TDR) event
Too many WebGL contexts open across tabs (browsers limit to ~16 active contexts)
GPU out of memory from complex scenes, large textures, or many draw calls
Background tab WebGL context killed by browser to save resources
Outdated GPU driver with WebGL compatibility bugs

Steps

1Refresh the page to request a new WebGL context
2Close other tabs using WebGL (3D games, maps, visualizations) to free GPU resources
3Update GPU drivers to the latest version from the manufacturer
4For Chrome: check gpu status at chrome://gpu for driver issues
5Reduce browser GPU memory usage: close unnecessary tabs and restart the browser