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

Posted to jira@arrow.apache.org by "Rok Mihevc (Jira)" <ji...@apache.org> on 2023/01/11 07:08:03 UTC

[jira] [Commented] (ARROW-250) Fix for ARROW-246 may cause memory leaks

    [ https://issues.apache.org/jira/browse/ARROW-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17657284#comment-17657284 ] 

Rok Mihevc commented on ARROW-250:
----------------------------------

This issue has been migrated to [issue #15592|https://github.com/apache/arrow/issues/15592] on GitHub. Please see the [migration documentation|https://github.com/apache/arrow/issues/14542] for further details.

> Fix for ARROW-246 may cause memory leaks
> ----------------------------------------
>
>                 Key: ARROW-250
>                 URL: https://issues.apache.org/jira/browse/ARROW-250
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Java
>            Reporter: Abdel Hakim Deneche
>            Assignee: Abdel Hakim Deneche
>            Priority: Major
>             Fix For: 0.1.0
>
>
> The fix for ARROW-246 involves allocating an inner vector in the constructor of another vector. This is not recommended.
> A better fix is to make sure we call allocateNew() on the vector after we allocate it



--
This message was sent by Atlassian Jira
(v8.20.10#820010)