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/12 22:01:00 UTC

[GitHub] leleamol commented on issue #13437: Memory leak in c++ api

leleamol commented on issue #13437: Memory leak in c++ api
URL: https://github.com/apache/incubator-mxnet/issues/13437#issuecomment-462953904
 
 
   @aravindhv10 
   I looked at the valgrind log and it seems valgrind terminated itself by throwing SIGILL signal.
   This is happening just after libmxnet.so is getting loaded.
   
   Similary the cv related allocations that you have mentioned are done when opencv shared library is getting loaded during execution.
   I am not seeing evidence in valgrind.log that exec->Backward() is leaking the memory.  The program.cpp must have died while executing MXPredCreate() call itself.
   
   Did you get chance to monitor the RSS memory and VMSize when the program was running by itself (i.e not in valgrind)?
   
    
   

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