WebGPU on EC2 Windows - requestAdapter Failed to create WebGPU Context Provider
10 views
Skip to first unread message
wenhan chong
unread,
4:45 AM (10 hours ago) 4:45 AM
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to blink-dev
Hi All,
While trying to run Chrome with WebGPU on EC2 Windows instances unattended, I noticed inconsistent behaviors for WebGPU. Each browser session is a coin flip between having and not having WebGPU. The code fails to get adapter from navigator.gpu.requestAdapter. Errors show "Failed to create WebGPU Context Provider". This only happens when I run the tests unattended. After connecting to the EC2 instances through remote desktop, the same set of automated tests are able to render WebGPU consistently without issues. I also noticed several error messages including GPU process crash in chrome://gpu when running unattended. I have attached dxdiag output and chrome://gpu reports for both unattended sessions and remote desktop connected sessions. Trying to understand what is causing the inconsistency and if there are additional options required to run WebGPU on unattended EC2 windows instance.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to blink-dev, wenhan chong
Attaching additional output from chrome://gpu showing errors from failure in unattended browser sessions. Some of the browser sessions are also not able to detect nvidia T4s, falling back instead to ANGLE swiftshader device.