lidavidm commented on issue #41782: URL: https://github.com/apache/arrow/issues/41782#issuecomment-2126346519
I think we need to do two things: - tearDown needs to run after each test to narrow down the scope of the leaked memory. - We need to properly add debug information to print out the leaked buffer's retain/release history and where it was allocated. We optionally track this info and it should be enabled in CI and the error message should be enhanced. @vibhatha -- 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]
