-
Notifications
You must be signed in to change notification settings - Fork 142
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.File for particular file works on v0.10.4 crashes on v0.10.5 #1041
Comments
Hmmm, I don't see any crash on apple m1 with Julia 1.8.1. Can you share your platform + Julia version? |
Julia v"1.7.3" (sorry didn't occur to me that I am a bit behind there. My job hasn't needed much coding the last few months) |
Can you post the full crash you're seeing? Usually that can help us know if there's something in CSV.jl going wrong, or a more general Julia issue (that may have been fixed since 1.7.3). |
|
I first had this happen in Pluto. Figured I would post the REPL output when the Pluto process crashes on the off-chance it is helpful.
But my wildly uninformed guess is that this is all Pluto stuff reacting to the crash, but info never hurts. |
I am having a similar issue with a file that worked on v0.10.4 but not on v0.10.5. I get the exact same exit code (3221225477 ) in vscode and the terminal crashes. If I try to open the file in a external REPL with CSV.File it crashes the REPL and closes it. This is the file: I am on Windows 10 Intel Core i7 with Julia 1.7.3. |
If either of you would be willing to try out a new PR I'd really appreciate it to see if it fixes your issue. You can try the PR out by doing: ] add CSV#jq/revert_precompile then reloading your REPL and trying to load the file. |
I tried this PR and it fixed the issue with my file. I was able to load the file at the REPL as expected. |
Ok, I've merged the PR; I put up another PR to hopefully fix a different memory leak issue, so once that's merged, I'll tag a new release. Thanks all. |
with v0.10.4 running
CSV.File("brokenfile.txt",header=9)
works appropriately. On v0.10.5 it crashes the process. I don't have time today to trim down the file to find what feature is causing the problem but may have a chance in a week or two. In the meantime I have attached the (unfortunately moderately sized) file.brokenfile.txt
The text was updated successfully, but these errors were encountered: