-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Crash on master with CategoricalArrays #18343
Comments
Turns out the line that triggers the crash is this one, from Base.convert{T}(::Type{Ref}, x::CategoricalValue{T}) = RefValue{T}(x) |
Oops, actually it's this one, from the same file:
|
Likely related to #16883, unlikely dup of #18299 Reduced code. __precompile__(true)
module CategoricalArrays
immutable Pool{R,V}
valindex::Vector{V}
end
immutable Value{T,R}
pool::Pool{R,Value{T,R}}
end
Base.convert{S}(::Type{Nullable{S}}, ::Value{Nullable}) = 2
Base.convert(::Type{Nullable{Value}}, ::Value{Nullable}) = 2
Base.convert{T}(::Type{Ref}, ::Value{T}) = 3
end |
AFAICT it also happens without precompilation enabled. |
It doesn't happen with precompilation off for me and the reduced case does have a recursive type so it's likely missing case from #16883. Note that removing |
this is similar to #16767, but it found a slightly different way to recurse :/ |
it seems to be unnecessary fix #18343
FYI, I'm still seeing crashes on current CategoricalArrays release (0.0.5) on julia 0.4.7. Both travis and locally. |
Also see the travis log here where we see it directly with CategoricalArrays when precompile is turned on. |
I don't think the fix is backported |
At leas this was closed by #18534 |
How backportable is that? |
..... Well, if you check that PR it already has backport 0.5 label applied so at least that's something |
Sorry, I meant backporting to 0.4. But since we don't get the crash on 0.5, that must be a different bug and fix. |
I'm getting a crash both with latest master and with 0.4.6 after loading CategoricalArrays.jl and calling
gc()
. You can get the code from thenl/crash
branch.Is this a duplicate of #18299?
The text was updated successfully, but these errors were encountered: