laggy issue of code editor in R2018b

25 views (last 30 days)
Yan Zhang
Yan Zhang on 30 Sep 2018
Commented: Jonas Hofbauer on 23 Apr 2022
I am using Macbook Pro 2014. 2.6Ghz i5 processor, 8GM 1600Mhz memory. I installed two versions of matlab, 2015a and 2018b. When I edited my codes in 2015a, everything is fine. However, running 2018b on the same machine, the code editor is very laggy. By "laggy", I mean when I simply tried to move the cursor or type some texts, it may respond after 1-2 seconds. Sometimes, the left bottom corner popped out info "processing...". I didn't see this info in the previous matlab version. Is the new version running something new in the back to cause this laggy issue? Am I the only one having this problem?
Yan Zhang
Yan Zhang on 2 Oct 2018
Thanks,guys! Someone tested it on macbook pro 2018 and it was fine there. I guess I'll simply go back to R2018a.

Sign in to comment.

Answers (4)

Kris Fedorenko
Kris Fedorenko on 3 Oct 2018
Edited: Kris Fedorenko on 3 Oct 2018
There were instances of similar behavior in R2018b caused by the Magnet app. Turning it off should resolve the issue. Alternatively, you should be able to use keyboard shortcuts with no delays.
Jonas Hofbauer
Jonas Hofbauer on 23 Apr 2022
When Matlab is open, you can go into the Magnet settings via the menu-bar dropdown and tick "Igonre Matlab" – resolved the issue for me!

Sign in to comment.

Fan Zhang
Fan Zhang on 27 Jun 2019
I encoutered the same problem on both r2018b and r2019a. The solution is to turn off Magnet.
Hope it helps.

Daniel Pantea
Daniel Pantea on 22 Oct 2018
Edited: Daniel Pantea on 22 Oct 2018
Seems not only MAC is affected. I have same delays in Windows 7 x64. Tested same script and: - with R2018b it needed 23.4s to process the data. - with R2018a it needed 17.21s to process the same data. I have to go back to R2018a as in some situations the display gets unresponsive for seconds with R2018b! Hope they come with some patches, else this is a step back...
Daniel Pantea
Daniel Pantea on 25 Oct 2018
I got great help from support and they identified a place of optimization which reduced the consumed time about 10 times! Details are below and after that the elapsed time difference from 2018b vs 2018a was insignificant:
  • 17a: 1.931015 seconds.
  • 18a: 2.253766 seconds.
  • 18b: 2.268560 seconds.
Here's detail of the improvement (which are specific to my case) I received from support:
Around line 775 in the SCRIPT.m, there is a very tight loop:
for i = 1:N1
k = min(i, mean_len);
my_mean = (my_mean*(k-1)+hUI.preprocessed{1}{ch}(i)) / k;
hUI.preprocessed{3}{ch}(i) = my_mean;
Using temporary variables to hoist some of the indexing out of the loop will make a huge difference:
tempVar3 = hUI.preprocessed{3}{ch};
tempVar1 = hUI.preprocessed{1}{ch};
for i = 1:N1
k = min(i, mean_len);
my_mean = (my_mean*(k-1)+tempVar1(i)) / k;
tempVar3(i) = my_mean;
hUI.preprocessed{3}{ch} = tempVar3;

Sign in to comment.

Yan Zhang
Yan Zhang on 23 Jan 2019
For anyone who is still interested, I updated my OS to Mojave (10.14.2) and the laggy issue of R2018b disappears.


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!