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

Posted to issues@mxnet.apache.org by "Denis Davydenko (JIRA)" <ji...@apache.org> on 2018/10/08 20:21:00 UTC

[jira] [Updated] (MXNET-731) Memory Management in Scala binding

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

Denis Davydenko updated MXNET-731:
----------------------------------
    Sprint: Scala/Java 1 (07/30-08/13), Scala/Java 2 (08/13-08/27), Scala/Java 4 (09/10-09/24), Scala/Java 5 (09/24-10/08), Scala/Java 6 (10/08 - 10/22)  (was: Scala/Java 1 (07/30-08/13), Scala/Java 2 (08/13-08/27), Scala/Java 4 (09/10-09/24), Scala/Java 5 (09/24-10/08))

> Memory Management in Scala binding
> ----------------------------------
>
>                 Key: MXNET-731
>                 URL: https://issues.apache.org/jira/browse/MXNET-731
>             Project: Apache MXNet
>          Issue Type: Story
>          Components: Apache MXNet Scala API
>            Reporter: Denis Davydenko
>            Assignee: Naveen Swamy
>            Priority: Major
>
> Due to C++ nature of MXNet, Scala binding has to take care about memory management and garbage collector for its users. Success criteria: Scala API users should not have to take special care about disposing objects created by MXNet and hence should not see memory leaks with their implementation of MXNet using Scala API binding.



--
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