Matlab 2019a on Windows 10 freezes during script

Hello,

I am using MATLAB 2019a on Windows 10, but Matlab for some reason keeps freezing after starting a script. Specifically, after starting the script, it first works fine for a minute or so, before the main Matlab window starts printing weird symbols in the command window (instead of the correct output that the script is supposed to print). What's confusing is that Matlab does not freeze always at the same stage of the script, so it's not a specific command/line within the script that's causing this error. Also, I am quite sure that it's not a memory issue, because I am using a powerful machine with 32GB RAM and the exact same script runs completely fine on another computer (Mac) that is 8 years old and has only 8GB RAM. Also, I can see in the windows task manager that none of the performance resources (CPU, memory, etc.) is even close to it's limits.

Any help or ideas is highly appreciated.

Thank you,

Matthias

[Jan]

We need any details. Can you post a minimal working example, which reproduces the problem? How does the output look like? Did you test the RAM already?

[Matthias Stangl]

Thank you for your quick response! I'm attaching two screenshots that show what happes after I've started the script (both show the Matlab main window, which is not displayed properly). In screenshot2, you'll see also the task manager window on top of the Matlab main window, which also shows that memory etc. is not close to any limits.

I've also run a RAM test (Windows 10 memory diagnostic) and there were no issues detected. Also I do not have any other issues with the computer (it's pretty new) even though I also use other computationally expensive programs (e.g. 3D modeling software) sometimes. Also, when Matlab freezes, all other processes/programs etc. continue working fine, so Windows itself does not have any issues, it's only the Matlab main window. Btw: It's not only a graphical problem, as the script also does not continue to process.

Unfortunately, I can't give you a short working example, as the script is calling many different functions. But I've had the error also with different completely independent scripts, so I also don't think it's something in this particular script. Also, as I've said before, the exactly same script runs fine on two different Mac computers that are both much less powerful.

[Matthias Stangl]

Actually, I do not even believe that the script itself stops working. I believe it's continuing to run but it just gets EXTREMELY slow. But the script does not produce any errors and the Matlab status is still "busy".

[Matthias Stangl]

I still have the same issue and did not find any (working) solution online. Any ideas what I could try to solve this?