stephenrawls commented on issue #13265: MXNet C++Interface reasoning leads to CPU memory leak URL: https://github.com/apache/incubator-mxnet/issues/13265#issuecomment-463931063 I see, thanks for background. I didn't look closely so just assumed it was about GPU memory. Re: "I cannot imagine what memory problems will be caused during destruction". I'm not an expert, but I think that in general destruction order is undefined for global variables and it can cause memory related problems if the memory an object needs during destruction has been freed before its destructor runs. Because the order of destruction is undefined things often seem to run fine until you get unlucky and the order changes. See the issue I mentioned earlier, or this one: https://github.com/apache/incubator-mxnet/issues/12613 No idea if it applies here or not though.
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
