zeroshade commented on pull request #11310: URL: https://github.com/apache/arrow/pull/11310#issuecomment-942444102
I figured out the cause of the issue, when using `WriteWithMetadata` from the Go flight library, if the schema message hadn't yet been sent yet it includes the metadata in the schema message in addition to the first record batch message. In the Java, it allocates the memory for the application metadata for the Schema message, but never cleans it up causing the allocator to see it as a memory leak and error out. So adding a check on schema messages to close out the app metadata solves that issue, which I've done here in order to fix the issue with Java as a flight consumer. -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
