pitrou commented on issue #44599: URL: https://github.com/apache/arrow/issues/44599#issuecomment-2477038567
Ok, so what this tell us is that there is no actual memory leak in Arrow (at least on this use case :-)), but the memory allocator may decide to hold onto some memory to make further allocations faster. Note that the memory is not *necessarily* unavailable to other applications. For example, the memory allocator might have set these memory areas as [`MADV_FREE`](https://man7.org/linux/man-pages/man2/madvise.2.html), which lets the kernel free the pages when it needs to, but not necessarily immediately. This all shows how complicated it is to get accurate memory footprint measurements on modern OSes... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
