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

Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2019/02/08 05:05:00 UTC

[jira] [Updated] (ARROW-4120) [Python] Define process for testing procedures that check for no macro-level memory leaks

     [ https://issues.apache.org/jira/browse/ARROW-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wes McKinney updated ARROW-4120:
--------------------------------
    Fix Version/s:     (was: 0.13.0)
                   0.14.0

> [Python] Define process for testing procedures that check for no macro-level memory leaks
> -----------------------------------------------------------------------------------------
>
>                 Key: ARROW-4120
>                 URL: https://issues.apache.org/jira/browse/ARROW-4120
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Python
>            Reporter: Wes McKinney
>            Priority: Major
>             Fix For: 0.14.0
>
>
> Some kinds of memory leaks may be difficult to unit test for, and they may not cause valgrind errors necessarily
> I had written some ad hoc leak tests in https://github.com/apache/arrow/blob/master/python/scripts/test_leak.py. We have some more of this in ARROW-3324. 
> It would be useful to be able to create a sort of "test suite" of memory leak checks. They are a bit too intensive to run in CI (since you may have to run something many iterations to see whether it leaks), but we could run them in a nightly build



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)