Will memory leaks happen when the MEX file contains new & delete or STL containers (C++)?

2 次查看（过去 30 天）
Eli4ph
Eli4ph 2017-9-5
编辑： José-Luis 2017-9-5
Memory Management in documentation says that mxCalloc and mxFree, instead of calloc and free in standard C library, should be used to manage memory.
However, it is sometimes unavoidable to use new & delete when using C++ classes in MEX file, as well as the automatic memory management of STL containers when using them.
Here comes the question. If the user sometimes interrupts the MEX file execution using Ctrl+C, and if the MEX file contains new & delete or STL containers, will memory leaks happen? If so, how to avoid memory leaks (with least extra work)?
  2 个评论
Philip Borghesani
Philip Borghesani 2017-9-5
编辑：Philip Borghesani 2017-9-5
SIGINT does not apply here. MATLAB will handle SIGINT and will throw a synchronous c++ exception when it is safe to do so. Under no circumstances should a MEX file attempt to install a signal handler doing so will interfere with MATLAB's signal handler and cause never ending grief.

请先登录，再进行评论。

请先登录，再回答此问题。

采纳的回答

Philip Borghesani
The short answer is: Put anything allocated with a standard allocator into a smart pointer (unique_ptr, shared_ptr,...) and never put a MATLAB allocated object (mxMalloc, mxCreate...) into a smart pointer or attempt to free one on object destruction and you will be fine.
Most of the documentation/API is written from the perspective of C and FORTRAN mex programming and has not been updated for C++ yet. If you are using a supported C++ compiler (I am not completely sure about minGW on Windows) then the normal C++ exception mechanism is used and destructors are run when ctrl-c is used in a mex file.
  2 个评论
Eli4ph
Eli4ph 2017-9-5
Great! So the extra work to avoid memory leaks is putting them into smart pointers? Also, forgive my bad understanding, what does 'attempt to free one on object destruction' mean? (I am not completely sure.)
José-Luis
José-Luis 2017-9-5
编辑：José-Luis 2017-9-5
Great. Learned something today.
So whatever cleanup is needed should be explicitly handled in the destructors?
And if memory is left dangling it will live in limbo until you exit Matlab?

请先登录，再进行评论。

更多回答（0 个）

类别

在 Help Center 和 File Exchange 中查找有关 启动和关闭 的更多信息

标签

产品

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!