-
Notifications
You must be signed in to change notification settings - Fork 140
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
CSV fails to compile #981
Comments
I got the same problem here.
and my version information is
|
We are currently giving a statistics course where we are using Julia and we are seeing a trend that people that are using Windows 11 are running into an error with precompiling the CSV package. I am not sure if this is also the case for your computers? |
What's the stacktrace? Would be good to know if it's the same. FWIW I'm on Windows 10, |
[ Info: Precompiling CSV [336ed68f-0bac-5ca0-87d4-7b16caf5d00b] |
Thanks, looks like it's the same thing then! Does repeatedly calling |
I had the same, I just kept insisting on |
After running using CSV at least 60 times the issue still persists |
The ccall in https://github.com/JuliaData/CSV.jl/blob/main/src/precompile.jl#L3 is breaking precompilation, don't know why, yet. Edit: Coincidence? 🤷♂️ |
After adding [email protected] and pining Parsers, CSV can be precompiled. |
Following your suggestion, CSV can be precompiled successfully. |
Hi all, Can confirm I've seen this too, though the file mentioned is different. Scripts with Which worked once I re-started Julia. The stacktrace I had been getting was: -
|
Same problem here on my Windows system, triggered when Parsers updated from v2.2.0 to v2.2.2. And the same fix worked for me except that I did it by fixing the version of Parsers in Project.toml:
If you can't find the root of the problem I think you should consider tagging a quick release of CSV.jl that constrains the Parsers version in a similar way. Many people seem to be having this issue and CSV.jl is pretty important in Julia's ecosystem. |
Parsers.jl v2.2.2 did change what gets called during precompilation, so that could well be related it might be helpful to know if anyone sees this issue on v2.2.1 |
From the random/hard to reproduce nature of this my guess would be a memory problem on Windows, especially with reports that using a terminal instead if vscode/atom fixes it? I imagine the combination of Parsers.jl and CSV.jl precompilation would use a lot of memory. We should probably rewrite those Parsers.jl functions and These functions are sometimes 100s of lines each with too much type instability. |
For what it's worth, I had the problem while running Julia inside Windows Terminal. I didn't try it in VScode. |
Does anyone know if this is Julia version specific? I'm getting this problem in VSCode on v1.7.1 and v1.7.2. It's quite annoying since not only does precompilation not work in VSCode, I also see random (what I assume are) segfaults when loading large-ish CSV files. All seems to work fine in Windows Terminal but when I connect it to VSCode as an external REPL, the language server frequently dies. |
Diagnosed to be causing CSV.jl precompile to fail on windows for an unknown reason (JuliaData/CSV.jl#981). Removing the precompiles for now until further investigation can be done to figure out the root cause.
Quite a few people have reported this recently:
(there's a discussion on Slack where three people are seeing it, and a Discourse discussion here [note the discussion initially is about the old Parsers issue, but further down people are reporting this new issue).
Unfortunately it's hard to reproduce because it appears it is generally solved by doing either
] build CSV
or just repeatedly callingusing CSV
.The text was updated successfully, but these errors were encountered: