-
Notifications
You must be signed in to change notification settings - Fork 83
Fetching DF shows up as memory corruption #489
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
@mauropagano thanks for your continued focus on dataframes. |
Client is linux, db is 19.x. |
Just realized I never provided an output example. Below is one from thick mode, thin reproduces too but need to try a few times (5-10 probably) Working case (commenting out
Example of incorrect output (
|
@mauropagano thanks for that. I had to change the connection handling before I could see it. Also using
I'll let @anthony-tuininga and @aosingh dig into it. |
I was able to reproduce this and it happens because of premature deallocation of the underlying |
What versions are you using?
3.1.0 on python 3.9.6 and 3.12.7
Is it an error or a hang or a crash?
Looks like memory corruption, running the code over and over at some point you see the same Arrow object printing junk (I don't think it goes back to db to re-run)
This fails CONSISTENTLY if the same connection is used twice (I'm not sure that's expected or not), but it also fails (if you try enough) with a new connection
What error(s) or behavior you are seeing?
Incorrect result, need to run a few times
Does your application call init_oracle_client()?
Reproduces in both thin and thick, thick seems easier to trigger
Include a runnable Python script that shows the problem.
The text was updated successfully, but these errors were encountered: