-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Open
Labels
ep:WebNNWebNN execution providerWebNN execution providerfeature requestrequest for unsupported feature or enhancementrequest for unsupported feature or enhancement
Description
Describe the feature request
Is there any plan to report more specific error code values for critical errors such as “device-removal” , “device-reset” and “out of memory”?
I looked into the ORT repo, I found that the OrtErrorCode values returned by ORT API like ORT_FAILand ORT_RUNTIME_EXCEPTION are somewhat general.
- OrtModelEditorAPI::CreateSessionFromModel method tries to catch all exceptions and converts them to
ORT_FAILat 1 - InferenceSession::Run method tries to catch all exceptions and converts them to
ORT_FAILat 2 orORT_RUNTIME_EXCEPTIONat 3
Relevant issue: #26606
/cc @fdwr @RafaelCintron @huningxin @skottmckay
Describe scenario use case
For our WebNN implementation in Chrome browser, we handle the OrtErrorCode values from ORT API, but we don’t know which values should be treated as critical errors, such as
“device-removal” , “device-reset” and “out of memory”, as defined at DXGI_ERROR. For these errors, WebNN needs to destroy the context and may even decide to kill the Chrome GPU process.
fdwr
Metadata
Metadata
Assignees
Labels
ep:WebNNWebNN execution providerWebNN execution providerfeature requestrequest for unsupported feature or enhancementrequest for unsupported feature or enhancement