[
https://issues.apache.org/jira/browse/ARROW-6490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated ARROW-6490:
----------------------------------
Labels: pull-request-available (was: )
> [Java] log error for leak in allocator close
> --------------------------------------------
>
> Key: ARROW-6490
> URL: https://issues.apache.org/jira/browse/ARROW-6490
> Project: Apache Arrow
> Issue Type: Task
> Components: Java
> Reporter: Pindikura Ravindra
> Assignee: Pindikura Ravindra
> Priority: Major
> Labels: pull-request-available
>
> Currently, the allocator close throws an exception that includes some details
> in case of memory leaks. However, if there is a hierarchy of allocators and
> they are all closed at different times, it's hard to find the cause of the
> original leak.
>
> If we also log a message when the leak occurs, it will be easier to correlate
> these.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
