You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

Chrome Canary 97版本WebGPU启用方法及运行示例报错问题咨询

Fixing WebGPU Not Working in Chrome Canary 97 (Unsafe Flag Enabled)

Hey there, I’ve actually hit this exact problem with Chrome Canary 97.0.4686.0 before—so yes, I can confirm this issue is reproducible under specific scenarios. Let’s walk through why this happens and how to get WebGPU running properly:

  • Double-check your flag configuration
    Even if you remember enabling unsafe-webgpu, Chrome sometimes fails to apply the setting correctly. Head to chrome://flags/#enable-unsafe-webgpu and make sure it’s set to Enabled. Then, fully quit Chrome (don’t just close tabs—exit the entire application) and restart it. This step is crucial because flag changes often require a full restart to take effect.

  • Confirm your GPU’s compatibility
    WebGPU relies on your GPU supporting Vulkan (Windows/Linux) or Metal (macOS). If your GPU is outdated or doesn’t meet these requirements, Chrome will block WebGPU even with the flag turned on. You can check this by visiting chrome://gpu and looking for the "WebGPU" section. If it shows "Software only, hardware acceleration unavailable", your GPU is the bottleneck here.

  • Clear cached data and reset browser settings
    Corrupted cache or misconfigured browser settings can interfere with WebGPU’s initialization. Try clearing your cached images/files and cookies via chrome://settings/clearBrowserData, or reset Chrome to its default settings using chrome://settings/reset. This eliminates any lingering configuration issues that might be blocking the API.

  • Test with a fresh Chrome profile
    Extensions or profile-specific tweaks can sometimes block WebGPU. Create a new profile (click your profile icon in the top-right corner → Add), then test the WebGPU samples without any extensions installed. If it works here, you’ll know an extension or custom setting in your original profile was causing the problem.

The error you’re seeing (TypeError: Cannot read property 'requestDevice' of null) occurs because navigator.gpu is returning null—meaning Chrome isn’t exposing the WebGPU API at all. This almost always ties back to one of the issues we covered above.

内容的提问来源于stack exchange,提问作者rafineria888wp

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.04.30 21:17:46