You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an old ONNX model translated from tensorflow with tf2onnx a while ago.
It always used to run fine in the previous version (<1.17) but I now hit an Access Violation during the inference.
In 1.16.3 everything works fine. The package is onnxruntime-gpu.
You can find the model here
The error happens during the inference and not at the creation of the InferenceSession. While creating the inference session the models seems to be correctly put on GPU memory and the error happens when calling .Run
Also the error does not happen when I specify CPUExecutionProvider in the providers list.
To reproduce
The following code runs fine in 1.16.3 but not in 1.17.1
snnn
changed the title
[CUDA][1.17.1][Windows][Regression] Access Violation in an inference session Run
[CUDA][1.17.1][Regression] Access Violation in an inference session Run
Mar 5, 2024
Describe the issue
I have an old ONNX model translated from tensorflow with tf2onnx a while ago.
It always used to run fine in the previous version (<1.17) but I now hit an Access Violation during the inference.
In 1.16.3 everything works fine. The package is onnxruntime-gpu.
You can find the model here
The error happens during the inference and not at the creation of the InferenceSession. While creating the inference session the models seems to be correctly put on GPU memory and the error happens when calling
.Run
Also the error does not happen when I specify
CPUExecutionProvider
in the providers list.To reproduce
The following code runs fine in 1.16.3 but not in 1.17.1
Urgency
No response
Platform
Windows
OS Version
11
ONNX Runtime Installation
Released Package
ONNX Runtime Version or Commit ID
1.17.1
ONNX Runtime API
Python
Architecture
X64
Execution Provider
CUDA
Execution Provider Library Version
CUDA 11.8
The text was updated successfully, but these errors were encountered: