matlab 2014b on Yosemite, high CPU%

Hi there,

I just upgraded my OSX to 10.10 and installed the 2014b. But the matlab uses about >100% of CPU after startup, and sometime it goes up to 500%..... and the matlab freezes up.

I do notice that on the bottom of "current folder" dialog, it says " getting status for files " and it keeps doing it.

Does any of you guys know what could have caused this problem?

Thanks,

Answer 1

[Bruno Pop-Stefanov]

The getting status for files message appears because of the Source Control integration in the Current Folder browser. Try disabling Source Control if you are not using it.

To disable Source Control:

1. Click Preferences in the Home tab of the MATLAB Desktop
2. Go to MATLAB > General > Source Control and select None
3. Click OK

Now restart MATLAB and you shouldn't see a spike in CPU usage anymore. Let me know if you still do.

[Yanjun Yang]

Hi, I'm facing the same problem except I'm still on OSX 10.9.5.

After I upgraded my Matlab to 2014b, I'm noticing that on the bottom of "current folder" dialog, it says "getting status for files" and it keeps doing it for hours.

And I tried the solution you gave here, it works. But what should I do if I need to use the source control?

Thanks

[Bernie]

I am still seeing the same high CPU usage and ~56GB of RAM usage (my computer only has 16GB...). I got the same issue using R2012a on Mac OS 10.10 Yosemite, but turning off source control seems to have resolved that problem. The high CPU usage still persists in R2014b. I have restarted Matlab and my computer multiple times. And done a RAM reset.

[TKeenan]

Fantastic Bruno - Thanks! I had the same problem - very high CPU usage (500%) on 2014b (and 2015a), but no problem with 2013b or 2014a. OS Yosemite. Noticed that 'getting status for files' was showing in the folder window during the periods of high CPU usage.

Following the steps above seems to have solved the problem.

[Jaime Batiz]

Turning off Source Control didn't help me. I'm working with a small .mat file (172KB) that contains a structure of structures, several levels deep. Just by loading it, and inspecting a structure with the Variable Viewer window, and then moving on to other applications makes Matlab's CPU % jump to 100%+ and slows it down to the point that it is unusable after 30 minutes (or so) of inactivity.

[Nicholas Bergantz]

This fixed it for me. Is Mathworks going to get around to fixing the underlying problem? 6years later?

Answer 2

[Anthony]

Hi all,

Same story here w/ updating to yosemite with r2014b - slow as molasses. This is ridiculous, particularly with any plots. Disabling source control helps to a minor extent.

Are there any work arounds or fixes?