Troubleshoot WebGL and rendering problems

If the test cannot start

The page content remains available when WebGL2 is missing. An unsupported message means the browser could not create the graphics context required by this workload. It is not a failed memory test. Check that your browser is current and that hardware acceleration is permitted by its settings and your organization’s device policy.

Try the same page in another browser on the same device. If one works and one does not, first investigate browser settings, extensions or graphics-driver support. On a managed machine, ask the administrator rather than bypassing policy. On a virtual machine or remote desktop, graphics capabilities may differ from a local session.

If the renderer is unexpected

Renderer information is supplied by the browser and graphics driver. It can be masked for privacy, translated through ANGLE, or show software rendering. An unfamiliar label does not establish that the card is counterfeit.

On a laptop with more than one GPU, check the operating system’s graphics preference for the browser, then restart the browser and confirm the renderer again. Do not change GPU routing midway through a comparison. Shared-memory GPUs do not have a browser-readable fixed pool of dedicated VRAM.

If FPS drops or the tab freezes

Start again at 256-pixel textures and one texture slot. Save unrelated work first. If the small workload runs, increase only one setting at a time. Close competing applications and keep the tab visible. A background tab can be throttled or paused, making its timing unsuitable for comparison.

If the context is lost, stop the run and reload before collecting another result. Context loss can arise from resource pressure, a graphics reset or browser lifecycle changes. It does not identify the failed component. The test checks resource creation and stops on a lost context instead of presenting the run as a successful diagnostic.

Check temperature and power using your operating system or the GPU vendor’s utility. This page cannot read sensors. If the entire system is unstable or shows unusual temperatures, stop adding load and investigate the system first.

If you see artifacts or driver resets elsewhere

Record the exact application, scene, driver version and settings that trigger the symptom. Return memory and core clocks to stock, remove undervolting, and reproduce that same workload. Then compare a known-good driver if the problem started after a driver change.

A texture problem isolated to one game can involve application data, shaders or a software bug. A problem across unrelated applications is stronger evidence for a system-level issue, but power delivery, cooling, system RAM and drivers remain possible causes. A native memory test with repeated verification failures is additional evidence, not a diagnosis made by this page.

Keep screenshots and error logs. If faults persist at stock settings, contact the hardware vendor or a qualified technician with the reproduction steps. Avoid opening the card or changing voltages simply because a browser score looks low.

Information to include in a bug report

A precise report lets us distinguish a website defect from a device-specific limitation. Please include:

• Page URL, browser and operating system versions.
• Renderer name shown by the test, or the exact unsupported message.
• Texture dimensions, count, filtering and duration.
• Whether the tab was visible and whether the issue reproduces with one 256-pixel texture.
• The actual behavior and any console error. Remove private information from logs before sharing.