MATLAB doesn't exit, all windows close, but MATLAB.exe persists in Task Manager
51 views (last 30 days)
Show older comments
Well, the title says it all. Is this a common problem? What could cause and fix this?
I'm on Win8x64 and I use R2014b. When I quit MATLAB, either by pressing the cross or typing
exit
in the command window, all open MATLAB windows close after a few seconds, but the process remains in the Task Manager. It takes a lot of memory too: the usual amount MATLAB uses (usually over 500MB). When I launch MATLAB again, I get a second MATLAB.exe and the first one remains unchanged. I can kill the process by force closing it in the Task Manager, but I'm not comfortable with doing that often and the extra clicks are just annoying.
0 Comments
Answers (1)
Debarati Banerjee
on 13 Apr 2015
Edited: Debarati Banerjee
on 13 Apr 2015
It is a known issue with MATLAB R2014b. As a workaround MATLAB can me made to terminate itself via a call to the operating system. You can place the following lines of code in a script named "finish.m" and place the script on the MATLAB path. The codes should be as follows:
id = feature('getpid');
if ispc
cmd = sprintf('Taskkill /PID %d /F',id);
elseif (ismac || isunix)
cmd = sprintf('kill -9 %d',id);
else
disp('unknown operating system');
end
system(cmd);
10 Comments
Tim Darrah
on 18 Jan 2023
Still a problem in 2022a!
The command
matlab -nodesktop -nodisplay -nosplash -logfile $DATE\_run\_$i.log -batch "try, run('simulation.m'), catch e, fprintf('%s', string(e.message)), end; exit;"
does not exit, even when "simulation.m" has finished running.
Well said @Raphael
"From my perspective, this is a serious bug and known issues since 7 years and still not yet fixed. Consider, this is a blocker for each realiable execution of MATLAB/SIMULINK on a CI platform. I cannot understand that for such expensive software."
This is an issue when using both the matlab gui as well as from the command line. Literally, @MathWorks Support Team, we just need matlab to quit when we say quit. Not have our windows close but then matlab utilize 100% of cpu until it is forcefully killed, not have a blinking cursor hang in a terminal and have matlab utilize 100% of cpu until it is forcefully killed.
Milo Fryling
on 1 Feb 2023
It's a showstopper for us in our lab. I isolated a line of code, where MATLAB process hangs around after termination if it is present, and not if it is removed. The author of the code says, " It looks like the issue relates to MEX and/or CUDA. The function you have isolated is the first time MATLAB calls compiled code...My first guess is that we somehow need to close the CUDA context that is created when you run GPU code."
The line of code is:
Yb = cyrebin( Y(:), Y_B, int_params_b, double_params_b, GPU_idx, det_type ); % , proj_time );
See Also
Categories
Find more on Software Development Tools in Help Center and File Exchange
Products
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!