Matlab and 'sandbox' process Peak CPU Usage in macOS Big Sur

26 views (last 30 days)
Matlab version: (R2021a) Update 3'
System Version: Big Sur 11.4 (20F71)
MacBook Pro: (13-inch, 2020, Four Thunderbolt 3 ports)
Processor: 2 GHz Quad-Core Intel Core i5
Memory: 16 GB 3733 MHz LPDDR4X
Graphics card: Intel Iris Plus Graphics 1536 MB
In the image bellow I pressed command+return to run the code and the sandboxed process started to peak. This happens all the time while using matlab. Sometimes even when just typing in in the code editor. I even tried closing all other applications in the system and run just Matlab, the problem persisted.
From time to time the sandboxd process peaks CPU usage and the entire Matlab becomes laggy, impossible to use. It is a recurrent problem. I tried installing 2020b version, but same thing happened. I'm not using Magnet or other window snaping tool.
I've sent a feedback to Mathworks under this identifier when it happened to froze once, forcing me to quit the application: Help troubleshooting recent MATLAB crash: 04938298 ref:_00Di0Ha1u._5003q1PuOu8:ref

Accepted Answer

Walter Roberson
Walter Roberson on 23 Jun 2021
This is a known issue in Big Sur 11.4 for M1.
I notice that you are not using M1; it is plausible that the same underlying problem is responsible (whatever that problem is.)
People have been reporting that R2021a Update 3 helps; I see you are already using that.
There is a bug report that indicates that some people may need to start MATLAB from Terminal to prevent crashes.
Jonathan Mynard
Jonathan Mynard on 19 Jan 2022
I am having the same problem but starting from the terminal does not solve it. (Using Mac Big Sur with Intel chip, R2021b and R2022a prerelease)

Sign in to comment.

More Answers (3)

Raphaël Nussbaumer
Raphaël Nussbaumer on 11 Dec 2021
Kill this process was the only solution which worked for me. I'm having to do that roughly every 30min.

Tim Lueth
Tim Lueth on 29 Dec 2021
Edited: Tim Lueth on 29 Dec 2021
The problem occurs frequently, even in 11.6.2 (Big Sur) with 2021b. I agree with Raphaël Nussbaumer that stopping the spindump task fixes the problem. For me, it occurs when the editor window is clicked from the command window or a file is opened with a double click, on OSX (MacBook Pro (13", 2020, 2.3 GHz quad-core Intel Core i7, 32 GB 3733 MHz LPDDR4X)

Matthew Johnson
Matthew Johnson on 29 Apr 2022
I'm not sure if what just worked for me will work for everyone -- it sounds like there could possibly be several closely-related variations on the same issue. But my 2021b was hanging on startup similar to what others were getting. I tried launching from the command line without the desktop running ( /Applications/ -nodesktop ) and then running the desktop command from within the terminal. When I did that, I got an error message about my desktop layout configuration XML file being corrupted, and that MATLAB was going to use the default configuration. I went ahead and re-positioned my window and panes, and then exited MATLAB and restarted the usual (non-command-line) way, and it started up just fine (and it appeared to have successfully saved my desktop layout). Again, not sure if others are having the same issue for the same reason, but perhaps this will fix some cases?
  1 Comment
Tim Lueth
Tim Lueth on 8 Jun 2022
I have tried this. Unfortunately, it did not help to fix the spindump/sandbox problem on 2021b and OSX10.16.

Sign in to comment.




Community Treasure Hunt

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

Start Hunting!

Translated by