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

Posted to issues@mxnet.apache.org by "Kellen Sunderland (JIRA)" <ji...@apache.org> on 2018/09/21 15:56:00 UTC

[jira] [Updated] (MXNET-922) Memory leak within profiler

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

Kellen Sunderland updated MXNET-922:
------------------------------------
    Resolution: Fixed
        Status: Done  (was: To Do)

> Memory leak within profiler
> ---------------------------
>
>                 Key: MXNET-922
>                 URL: https://issues.apache.org/jira/browse/MXNET-922
>             Project: Apache MXNet
>          Issue Type: Improvement
>            Reporter: Kellen Sunderland
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> ASAN is reporting a memory leak within the profiler.  We're also getting memory increases when allocating engines in a tight loop. Looking at the detailed code I think we may be leaking DeviceStats structs that aren't cleaned up in other places in code.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@mxnet.apache.org
For additional commands, e-mail: issues-help@mxnet.apache.org