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
{{ message }}
Repository navigation
C Data import leaks native memory when the allocator runs out of space mid-import #1239
Describe the bug, including details regarding any error messages, version, and platform.
When importing a C Data array into a BufferAllocator that hits its limit part-way through a multi-buffer array, the producer's native memory leaks permanently.
The bug is in ReferenceCountedArrowArray.unsafeAssociateAllocation: it increments the reference count before calling wrapForeignAllocation. If wrapForeignAllocation throws (allocator over limit), nothing decrements that count, so the C Data release callback never fires.
Fix: move retain() to after wrapForeignAllocation succeeds.
Activity
GH-1239: Fix memory leak when C Data import hits allocator limit mid-…
fix: release the Arrow stream when importing it runs out of memory