MATLAB: Does a GUI application which was compiled with the MATLAB Compiler 4.0 (R14) contain a CPU leak

callbackcompiledcompilercpuguiguideleakMATLAB Compilerprocessorstandalone

I am building a stand-alone application with the MATLAB Compiler 4.0 (R14) which performs calls to a GUI application created with GUIDE. When this program is run in MATLAB, it works fine. However, after compilation, the application gradually uses more of the CPU and ties up the processor's resources for other applications.
Why does this CPU leak occur? Is there any solution to this problem?

Best Answer

This has been verified as a bug in the MATLAB Compiler 4.0 (R14) in the way that standalone programs handle the GUI initialization routine. Typically, this occurs in an application which makes repeated direct calls to the GUI, and therefore repeatedly executes the GUI initialization routine.
Currently, to work around this issue, try calling the GUI only once in your application to open the GUI, and then use the GUI object handles directly to interface with the rest of your application.
Related Question