You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After execution of pyarrow.serialize, the interpreter crashes in the garbage collection routine.
This happens if a numpy array is returned in the custom serializer but there is no other reference to the numpy array. The reason this is not a problem in the current code is that so far we haven't created new numpy arrays in the custom serializer.
I think the problem here is that the numpy array hits reference count zero between the end of SerializeSequences in python_to_arrow.cc and the call to NdarrayToTensor. I'll push a fix later today, which just increases and decreases the reference counts at the appropriate places.
The problem happens with the following code:
After execution of pyarrow.serialize, the interpreter crashes in the garbage collection routine.
This happens if a numpy array is returned in the custom serializer but there is no other reference to the numpy array. The reason this is not a problem in the current code is that so far we haven't created new numpy arrays in the custom serializer.
I think the problem here is that the numpy array hits reference count zero between the end of SerializeSequences in python_to_arrow.cc and the call to NdarrayToTensor. I'll push a fix later today, which just increases and decreases the reference counts at the appropriate places.
Reporter: Philipp Moritz / @pcmoritz
Assignee: Philipp Moritz / @pcmoritz
PRs and other links:
Note: This issue was originally created as ARROW-1695. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: