You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Pindikura Ravindra (Jira)" <ji...@apache.org> on 2019/09/09 09:14:00 UTC

[jira] [Created] (ARROW-6490) [Java] log error for leak in allocator close

Pindikura Ravindra created ARROW-6490:
-----------------------------------------

             Summary: [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


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)