Resolving Low WebGL Frame Rates in Chrome by Adjusting failIfMajorPerformanceCaveat and Updating Integrated GPU Drivers

Background

A colleague observed that a simple WebGL program in Chrome ran at only single‑digit frame rates.

The console showed that pixi.js had set the failIfMajorPerformanceCaveat flag to true, causing getContext to fail and return null. Setting the flag to false allowed the context to be created successfully.

Code Example

// Success
var c = document.createElement("canvas");
c.getContext("webgl");

// Failure
var c = document.createElement("canvas");
c.getContext('webgl', {
  antialias: false,
  depth: false,
  failIfMajorPerformanceCaveat: true,
});

Explanation of the Parameter

If failIfMajorPerformanceCaveat is true, the browser will abort context creation when it determines that the resulting WebGL context would perform dramatically worse than a native OpenGL application, for reasons such as unstable GPU drivers or forced software rasterization.

Analysis

The machine is new, so OpenGL support should be fine. Chrome is up‑to‑date, but the integrated graphics driver was missing, showing only "Microsoft Basic Display Adapter" in Device Manager. Updating only the Nvidia MX250 driver did not help because the system was still using the integrated GPU.

After downloading and installing the Intel 10th‑gen integrated graphics DCH driver, the Device Manager listed "Intel(R) UHD Graphics" instead of the basic adapter. Windows became smoother, and Chrome now reports 60 fps for the WebGL application.

Conclusion

The issue was caused by an absent or incorrect Intel integrated GPU driver, which triggered the failIfMajorPerformanceCaveat check in WebGL. Installing the proper driver resolved the performance problem.