Matlab 2023b crash when I close a plot

111 views (last 30 days)
Marco
Marco on 25 Nov 2023
Commented: Siyuan on 21 May 2024
On macbook pro M1 whit the new MacOS Sonoma, Matlab 2023b crashes (or rather hangs/becomes unresponsive) everytime I close a figure manually, i.e. click the red cross on the figure window. Close all works fine though.
  5 Comments
the cyclist
the cyclist on 9 Mar 2024
Edited: the cyclist on 9 Mar 2024
This thread is the more complete discussion of this issue.
MacOS update 14.3.1 resolved this issue for many folks.

Sign in to comment.

Answers (3)

the cyclist
the cyclist on 25 Nov 2023
Edited: the cyclist on 25 Nov 2023
Known issue (among some others with Sonoma). See this thread.
I have had success closing figures "manually" if I put the focus on a different window first, before closing.
  2 Comments
Ruben Almeida
Ruben Almeida on 22 Feb 2024
This is the only thing that works for me.
the cyclist
the cyclist on 22 Feb 2024
In the thread I mentioned, it has been noted that the most recent Sonoma update seems to have resolved this bug.

Sign in to comment.


Thomas
Thomas on 14 Feb 2024
I Tried using command+W and it seems to fix the problem

Binod
Binod on 18 Dec 2023
Edited: Walter Roberson on 18 Dec 2023
One silly technique that I applied on "MacOS_M1_13"_sonoma14.2
% Specify the folder to save all the figures in your desired format(s) and use later
saveFolder = '/Users/practice/mode folder/figures';
% Create the folder if it doesn't exist
if ~exist(saveFolder, 'dir')
mkdir(saveFolder);
end
% Save all open figures in the specified formats
figHandles = findobj('Type', 'figure');
for i = 1:numel(figHandles)
% Save as JPG
saveas(figHandles(i), fullfile(saveFolder, ['figure_', num2str(i), '.jpg']));
% Save as FIG
saveas(figHandles(i), fullfile(saveFolder, ['figure_', num2str(i), '.fig']));
% Save as PNG
saveas(figHandles(i), fullfile(saveFolder, ['figure_', num2str(i), '.png']));
end
close all %if you are able to generate figs. already
  2 Comments
Peter Drummond
Peter Drummond on 11 Feb 2024
Edited: Peter Drummond on 11 Feb 2024
This is surely just plain ridiculous. Mathworks has known of this problem for years. Actually, it is pretty serious, with all work arounds causing many additional problems. For example, you can't, in my experience use 'close all' in a program, which I do use, without triggering the spinning circle of death.
Apparently it is a Java problem, but Matlab requires an obsolete Java to run. They don't seem concerned that they market a very expensive professional program which repeatedly crashes. If it was a 737, perhaps they would fix it? Oh, I forgot, Boeing did the same exact thing!
Is this a US problem with executives? You know, it costs money to fix things, so lets not bother, it might impact my bonus?

Sign in to comment.

Categories

Find more on Environment and Settings in Help Center and File Exchange

Community Treasure Hunt

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

Start Hunting!