You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mxnet.apache.org by GitBox <gi...@apache.org> on 2019/02/15 06:39:28 UTC

[GitHub] arcadiaphy edited a comment on issue #13265: MXNet C++Interface reasoning leads to CPU memory leak

arcadiaphy edited a comment on issue #13265: MXNet C++Interface reasoning leads to CPU memory leak
URL: https://github.com/apache/incubator-mxnet/issues/13265#issuecomment-463925092
 
 
   @stephenrawls The object pool is used to quickly allocate variables when threaded engine schedules computing operations, so it's not related to GPU memory.
   
   I think the object pools will only be destructed at program exit, so I cannot imagine what memory problems will be caused during destructing. I have re-added the free operation several weeks ago, and no problems are found in my using process.
   
   After fix this memory pool issue, some ASAN memory tests should be set up in CI to avoid memory leaks in C++ interface.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services