-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: read_csv segfault #5664
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
Comments
This is a C parser problem. Python parser appears to correctly handle names of lengths 1 and up. |
gr8 care to submit a PR? |
Yeah, I'm working on it. Isolated problem (#tokens < expected causing read from out of bounds) and working on fix. |
@guyrt progress on this? |
My fix hit a road block. I'll try to return to this once I free up some time. |
Hi, Not totally sure, but I think this one is related too:
Crashes about 50-80% of time, gives some NaN in other cases. Reproduced on OS X and Ubuntu, Pandas 0.13.1 and 0.14.1 |
Reproduced @cstenac 's example on windows as well. Note first example, where we just loaded in whatever from memory. That's concerning.
That does appear to be same issue: the C engine computes an expected size and reads until it fills that size. |
If there are two implementations of this and one is broken, shouldn't the other one be the default? |
Hello, I am not sure this is the same issue but the following snippet causes a segmentation fault on three machines I have tried (all running ubuntu). I have the same problem whenever I try to load a large csv file. However, if I load the file in chunks (using chunksize=...), there is no problem. Also, this problem doesn't occur if I use the python engine. I am using pandas 0.20.1
output:
|
try a newer version 0.20.3 and master |
same issue with 0.20.3 but not on master. Sorry, I should have checked that first |
np @jeromedockes great! |
Came across this when trying to parse a poorly-formatted csv file and got the number of columns wrong. Mostly it segfaults; sometimes it produces a broken last row.
When it doesn't segfault it tends to produce
The text was updated successfully, but these errors were encountered: