lidavidm commented on issue #35928: URL: https://github.com/apache/arrow/issues/35928#issuecomment-1579319327
Hmm, I'm surprised that worked at all before, since that basically asks the child allocator to reserve `Long.MaxValue` bytes immediately on creation, which would then make further allocations fail (since there's nothing left to be allocated), unless you only used the child allocator for allocations after that point perhaps. Without being able to debug the program itself, though, it's hard to say in general. Were there other exceptions? It's quite possible that an allocation failing could have led to a bug where something gets freed twice during cleanup. -- 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]
