-
Notifications
You must be signed in to change notification settings - Fork 7.1k
Failed to load image extension - Windows CUDA 11.7 #7185
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
Comments
This issue seems to be mitigated by:
|
It's a good old #4894 |
Another fun fact, @ptrblck , is this expected? |
It seems it was available in CUDA 11.7: https://anaconda.org/nvidia/libnvjpeg/files?version=11.7.2.34, so I'll check if this change is expected for Windows. |
Yes, it seems to be expected based on a response from the |
Thank you @ptrblck , this means we need to include dev packages for all libraries that we link dynamically with |
I'm trying to build torchvision 0.15.2 with cuda 11.7 and pytorch 1.13.1 on windows and hitting this issue. My environment has the following versions and is hitting this warning on package import, I tried adding libnvjpeg-dev and libnvjpeg from the nvidida channel but the warnings still are thrown on import with windows popup alerts, if they were just warnings it would be fine but the windows pop up makes this unusable in a CI system.
|
Thanks for the quick attention @NicolasHug! Unfortunately we are stuck on pytorch 1.13.1 but are also moving to py311 this release so I don't think we have a supported torchvision version we can use from pypi's wheels. Similar to this issue with using pytorch lts and torchvision: pytorch/pytorch.github.io#828 I think we'd have to revert to torchvision 0.14.x for our version of pytorch and try to build from source for py311 but that probably isn't supported. |
🐛 Describe the bug
I observe following failures
https://github.com/pytorch/builder/actions/runs/4104686412/attempts/3
Windows CUDA 11.7, python 3.8-3.10
Its same failure as: #7036
But now on windows.
cc @pmeier @NicolasHug @malfet
Versions
nightly
The text was updated successfully, but these errors were encountered: