Skip to content
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

Library handle creation close to OOM fails with ERROR_NOT_INITIALIZED #264

Closed
maleadt opened this issue Jul 1, 2020 · 0 comments · Fixed by #268
Closed

Library handle creation close to OOM fails with ERROR_NOT_INITIALIZED #264

maleadt opened this issue Jul 1, 2020 · 0 comments · Fixed by #268
Labels
bug Something isn't working cuda libraries Stuff about CUDA library wrappers. good first issue Good for newcomers

Comments

@maleadt
Copy link
Member

maleadt commented Jul 1, 2020

We have a fix for CUDNN handle creation failing with NOT_INITIALIZED, but it turns out all libraries can misreport failed allocations like that: https://gitlab.com/JuliaGPU/CUDA.jl/-/jobs/619182782, tensorflow/tensorflow#5354

@maleadt maleadt added bug Something isn't working good first issue Good for newcomers cuda libraries Stuff about CUDA library wrappers. labels Jul 1, 2020
@maleadt maleadt changed the title OOM handle creation Library handle creation fails close to OOM with ERROR_NOT_INITIALIZED Jul 1, 2020
@maleadt maleadt changed the title Library handle creation fails close to OOM with ERROR_NOT_INITIALIZED Library handle creation close to OOM fails with ERROR_NOT_INITIALIZED Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cuda libraries Stuff about CUDA library wrappers. good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant