-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CUDAExecutionProvider] Regression from ORT 1.15.0 onwards: Compute MatMul dimension mismatch #18692
Comments
I guess one may compile with |
This issue has been automatically marked as stale due to inactivity and will be closed in 30 days if no further activity occurs. If further support is needed, please provide an update and/or more details. |
Hi @yufenglee @tianleiwu, this issue is not stale and reported by user for an other architecture (table-transformer), with |
The issue is resolved in the main branch. I did reproduce it in 1.17.1:
So the issue is caused by some basic level graph optimization. If there is time, some debugging (by disabling basic level graph optimization one by one) can find which optimizer is the cause. |
Thanks a lot @tianleiwu |
Hi all, is this resolved in 1.17.3 released 2 days ago? @tianleiwu |
Describe the issue
Hi, I noticed a regression in
onnxruntime-gpu==1.15.1
andonnxruntime-gpu==1.16.3
(no problem ononnxruntime-gpu==1.14.1
.The following code runs fine on
CPUExecutionProvider
for all three ORT versions, but fails onCUDAExecutionProvider
for1.15.1
and1.16.3
.with the error:
To reproduce
As above. Reproduce with https://huggingface.co/fxmarty/bugged-detr-ort-cuda/tree/main
Using CUDA 11.7, which should be compatible according to https://onnxruntime.ai/docs/execution-providers/CUDA-ExecutionProvider.html
Urgency
medium
Platform
Linux
OS Version
Ubuntu 22.04
ONNX Runtime Installation
Released Package
ONNX Runtime Version or Commit ID
as above
ONNX Runtime API
Python
Architecture
X64
Execution Provider
CUDA
Execution Provider Library Version
CUDA 11.7
The text was updated successfully, but these errors were encountered: