-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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
BUG: MemoryError: Unable to allocate #39629
Comments
If your response is going to be that this issue is unfixable because code is unavailable, then I guess it's the end of the road for me using Pandas. In the latter case, I will also let all other Python developers know about this issue so they then can also avoid Pandas. To reiterate, there have been many instances of this issue reported here on GitHub and also on StackOverflow. It's a significant problem and it won't go away by pretending it doesn't exist. |
and these are exactly where? |
Issues: #35499, #31355, #29596, #28487 StackOverflow: search results More importantly, whenever Pandas reports a |
@impredicative a w/o reproducing example this is not a useful report. |
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
(optional) I have confirmed this bug exists on the master branch of pandas.
Code Sample, a copy-pastable example
Unfortunately this is not available since the errors occur exclusively over proprietary datasets which are very complex and large. It is not feasible to distill an example.
Problem description
I am seeing
MemoryError
exceptions all over the place on somewhat random lines. I am measuring the memory usage usingpsutil
to ascertain that there is however vast amounts of free memory on the node. These exceptions are making Pandas completely unusable for me. It's struggling with allocating 22 MiB when there is over 2 TiB of free memory available.Expected Output
These exceptions are not supposed to happen given there is sufficient free memory. There are many prior issues noting this exception, which is suggestive of severe continued bugs in Pandas.
Output of
pd.show_versions()
This is not entirely available since it's running exclusively in the cloud, but the salient versions are:
The text was updated successfully, but these errors were encountered: