I have reinstalled Debian Testing (upgraded from Bookworm) and I installed Matlab 2024a on it.
Now when I launch Matlab, MCR process (MCR 0 interpret) kicks off. It takes 5% CPU usage and Matlab command line is blocked – I cannot execute any command until I forcefully kill MCR process. Then I can use Matlab’s interpreter again.
The funny thing is that in my previous installation of Debian Testing (also based on bookworm) with Matlab 2023a this issue didn’t appear.Now when I test older versions of Matlab (2023, 2021) the same thing happens.I have reinstalled Debian Testing (upgraded from Bookworm) and I installed Matlab 2024a on it.
Now when I launch Matlab, MCR process (MCR 0 interpret) kicks off. It takes 5% CPU usage and Matlab command line is blocked – I cannot execute any command until I forcefully kill MCR process. Then I can use Matlab’s interpreter again.
The funny thing is that in my previous installation of Debian Testing (also based on bookworm) with Matlab 2023a this issue didn’t appear.Now when I test older versions of Matlab (2023, 2021) the same thing happens. I have reinstalled Debian Testing (upgraded from Bookworm) and I installed Matlab 2024a on it.
Now when I launch Matlab, MCR process (MCR 0 interpret) kicks off. It takes 5% CPU usage and Matlab command line is blocked – I cannot execute any command until I forcefully kill MCR process. Then I can use Matlab’s interpreter again.
The funny thing is that in my previous installation of Debian Testing (also based on bookworm) with Matlab 2023a this issue didn’t appear.Now when I test older versions of Matlab (2023, 2021) the same thing happens. debian, linux MATLAB Answers — New Questions

​