[
https://issues.apache.org/jira/browse/ARROW-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983718#comment-15983718
]
Julien Le Dem commented on ARROW-855:
-------------------------------------
[~fushengxu] To verify that your code calls close() or release() in the right
places, You can write a unit test that creates a RootAllocator first
(typically in before()) and closes the allocator at the end (in after()).
Closing an allocator that still has allocated resources will throw an exception.
FYI: I have added \{code\} blocks in your comments to make them more readable.
> Arrow Memory Leak
> -----------------
>
> Key: ARROW-855
> URL: https://issues.apache.org/jira/browse/ARROW-855
> Project: Apache Arrow
> Issue Type: Bug
> Components: Java - Memory, Java - Vectors
> Affects Versions: 0.1.0
> Environment: CentOS release 6.7+Indellij IDEA
> Reporter: xufusheng
> Priority: Critical
> Labels: test
>
> we create a memory table by arrow and the source data come from HBase.
> Create a memory table and then drop the table,there will be a memory leak.
> Hundreds of times,There will be OutOfMemoryError.
> anyone encounter similar problems?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
