You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Micah Kornfield (Jira)" <ji...@apache.org> on 2019/10/17 05:09:00 UTC
[jira] [Resolved] (ARROW-6898) [Java] Fix potential memory leak in
ArrowWriter and several test classes
[ https://issues.apache.org/jira/browse/ARROW-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Micah Kornfield resolved ARROW-6898.
------------------------------------
Fix Version/s: 0.15.1
1.0.0
Resolution: Fixed
Issue resolved by pull request 5671
[https://github.com/apache/arrow/pull/5671]
> [Java] Fix potential memory leak in ArrowWriter and several test classes
> ------------------------------------------------------------------------
>
> Key: ARROW-6898
> URL: https://issues.apache.org/jira/browse/ARROW-6898
> Project: Apache Arrow
> Issue Type: Bug
> Components: Java
> Reporter: Ji Liu
> Assignee: Ji Liu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0, 0.15.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> ARROW-6040 fixed the problem that dictionary entries are required in IPC streams even when empty, which only writes dictionaries when there are at least one batch. In this way, if we write empty stream and invoke ArrowWriter#close, the dictionaries are not closed leading to memory leak (they are closed after the write operation), and it’s really hard to debug, this problem was found by {{TestArrowReaderWriter#testEmptyStreamInStreamingIPC}} when I tried to close allocator after the test.
>
> Besides, there are several test classes have potential memory leak without closing allocator/vector/buf etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)