-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Open
Labels
ep:WebGPUort-web webgpu providerort-web webgpu providerep:WebNNWebNN execution providerWebNN execution providerplatform:webissues related to ONNX Runtime web; typically submitted using templateissues related to ONNX Runtime web; typically submitted using template
Description
This issue happens in WebNN ORT WebGPU EP.
reproduce steps
- Download the latest chrome canary
- Put the ORT dlls built with WebGPU (
onnxruntime.dll
,onnxruntime_providers_shared.dll
) under "C:\Program Files\ORT" (dxcompiler.dll
anddxil.dll
are not required because they are packed into chrome) - start the browser
.\chrome.exe --enable-features=WebMachineLearningNeuralNetwork,WebNNOnnxRuntime --allow-third-party-modules --webnn-ort-library-path-for-testing="C:\Program Files\ORT" --webnn-ort-ep-library-path-for-testing=fakepath --webnn-ort-logging-level=VERBOSE
- navigate to https://webmachinelearning.github.io/webnn-samples/image_classification/
- Select
WebNN (GPU)
Float32
MobileNet V2
, the test should run successfully - Refresh the page, repeat step 5, the process will crash. Navigate to
chrome://gpu
and scroll down to the bottom, you can see the logsGpuProcessHost: The GPU process crashed! Exit code: STATUS_ACCESS_VIOLATION.
debugging
From my debugging, it looks like the access violation is caused by accessing a null dawn::native::InstanceBase*
.
You can put the pdbs along with the ORT dlls and attach to the chrome GPU process if you want to debug.
fdwr
Metadata
Metadata
Assignees
Labels
ep:WebGPUort-web webgpu providerort-web webgpu providerep:WebNNWebNN execution providerWebNN execution providerplatform:webissues related to ONNX Runtime web; typically submitted using templateissues related to ONNX Runtime web; typically submitted using template