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
since new version: Flux throws error when for train! / update! even on quick start problem #2358
Comments
Can you try running the MWE in FluxML/Zygote.jl#1473 and see if you get a similar error? This looks like a problem on the CUDA.jl side, but to help them we should reduce it as much as possible. |
thank you for the hint - you are right, [email protected] triggers the following error: ERROR: WARNING: Error while freeing DeviceBuffer(400 bytes at 0x0000000205200a00):
CUDA.CuError(code=CUDA.cudaError_enum(0x000002bc), details=CUDA.Optional{String}(data=nothing))
Stacktrace:
[1] throw_api_error(res::CUDA.cudaError_enum) |
I have the same issue. With CUDA.jl v5.1.1 and Flux v0.14.7 on Win11 using Julia v1.10-rc3, all the demos with GPU failed with error |
Per FluxML/Zygote.jl#1473 (comment), the fix hasn't landed in a tagged version of CUDA.jl yet. |
I updated to the new version Flux 0.14.6 (and also CUDA 5.1.1) and got the illegal memory access error (see below) when using
train!
orupdate
machine: Windows Laptop
GPU: NVIDIA GeForce GTX 1050
CUDA Version: 12.0
Julia Version: 1.9.4
packages in environment:
I am aware of the new breaking changes in Flux and CUDA API, so
I just tested the quick start example and got the following error:
Downgrading to Flux v0.14.5 resolved the problem.
Any hints, what I am doing wrong with the new version?
The text was updated successfully, but these errors were encountered: