-
Notifications
You must be signed in to change notification settings - Fork 372
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
Core dumped, unreachable reached #2326
Comments
Tagging @quinnj I think this is an issue with
|
Hmmm, I'm not very familiar with the combine/reduce code; is there a more minimal repro on just the SentinelArray vector? |
got it! It seems to happen after a call to
|
I cannot reproduce it on 1.5:
|
I can reproduce on OSX |
|
I reproduced this with an rr trace and sent it to keno for investigation |
quinnj
added a commit
that referenced
this issue
Jul 27, 2020
Works around crash seen in #2326. The inferred return type of `groupreduce_init` is `Union{Vector{Any}, SentinelVector{Float64}}` and it seems the compiler then crashes when trying to correctly identify `U` from that union of types. Part of my conclusion here is based on the fact that if you remove all other argument type constraints and just make `groupreduce!` return `res` directly, it still crashes; thus, by deduction, the crash has something to do with the compiler having trouble with the `::AbstractVector{U}` argument type constraint/specialization. The work-around is pretty uncontroversial; we were already calling `eltype(res)` in several other places, and I've checked that it infers the same. I didn't add a test since this seems like such an obscure compiler bug that it doesn't really seem necessary for DataFrames to be testing core compiler behavior. Also note that this bug exists in Julia <= 1.5, so current Julia master (pending 1.6), which includes a number of compiler refactorings/changes, seems to have resolved whatever the issue was. cc: @Keno, @vtjnash, @JeffBezanson
Worked around in #2335 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a scary error I get from the following operation
I don't have an MWE available. If I try to isloate this by saving
d2
to a CSV and reading it in, this works fine.The text was updated successfully, but these errors were encountered: