-
Notifications
You must be signed in to change notification settings - Fork 206
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
Creating CuArray{Tracker.TrackedReal{Float64},1}
a few times causes segfaults
#121
Comments
That's fair. Can reproduce, happens on about the third call, probably during or right after a GC run. I'd guess this is a GPU pointer leaking into the CPU GC -- but I'm not sure how that could happen, since we've really locked down all of those conversions (FluxML/Flux.jl#581). |
Running with a gc debug build triggers an assertion, but no verification error:
|
Flux and CUDA.jl have changed a lot since this issue was filed, so going to close this as stale. Feel free to open a new issue if this still happens. |
I'm not sure if I should post it in Flux/Tracker or CuArrays. Please let me know if I should report it there.
Describe the bug
Executing
sum(CuArray(param.(ones(10))))
a few times (typically 2 or 3) causes segfaults. It does not happen if I runGC.enable(false)
first.To Reproduce
Expected behavior
I expect Julia to not die.
Build log
Environment details (please complete this section)
Details on Julia:
The text was updated successfully, but these errors were encountered: