R2013a editor slow to respond to edits?

Win7-64, 3+GHz i7, 32GB RAM, java heap maxed out, ...

I find the R2013a editor very slow to respond to keypresses on files that edit ok in R2012b.

The symptom is that keypressed get several characters ahead of the screen update, especially on inserts.

The editor start fine, edits ok, then the effect appears after a little editing, a few insertions, &c.

Yes, largish files, 2000 lines, callbacks & such generated by GUIDE so one file is sort of natural, &c.

Anyone found this & know anything that affects it?

[nanren888]

I have more than one install of this type & same effect.

[nanren888]

All files on local drives.

Answer 1

[Scott]

To follow up on this issue, I resubmitted a bug report about the slow editor with large files. I was told this is the fix:

http://www.mathworks.com/support/solutions/en/data/1-6MBFQL/index.html

You've got to be kidding. Doing what is suggested here not only requires a RESTART before and after editing a large file, but also disables EVERY feature that used to work fine with large file editing. For example, I can no longer jump to a function with the "f()" pull down menu!

This is a knee-jerk reaction by the developers to "fix" the problems introduced in recent releases with a hatchet instead of a scalpel. It makes editing large files painful in an entirely different way, and is a step backwards.

Please, developers, if you are listening, give me more control over what features I'm disabling. Certainly being able to jump to a function can't be that taxing on the editor. And please don't require me to restart to make changes! A little more effort and thoughtfulness into the fix to this problem would be greatly appreciated.

Answer 2

[Sean de Wolski]

This might be due to the Code Analyzer trying to analyze the entire file. Please shut it off in preferences and see if that helps:

Home Tab -> Preferences -> Conde Analyzer.

Answer 3

[nanren888]

Well, yes it affects it. Score one for a dependence. :)

With the code analyser off, it is not as slow, but still noticeably slow, much slower than R2012b, with the analyser on.

I loaded R2013a on a machine at home & get the same slow editor effect.

I like the code analyser/mlint.

Answer 4

[Tobias Otto]

I have the same problem (2013a (32Bit) on a Win7-32Bit), even with small files (three lines of code). Opening a file either with Editor Tab -> Open or on the command line (edit filename or open filename takes about 35 seconds! Disabling the Code Analyzer didn't help.

Does anyone have the same problem? My other installation of MATLAB 2011b still works fine.

Any help is appreciated.

Tobias

[Sean de Wolski]

Are you using directories on a network?

Answer 5

[Joseph MacGregor]

I agree that the R2013a editor is noticeably more laggy than the R2012b editor on the same machine with the same preferences. I'm on a MacBook Air so my machine is more modest than nanren888's, but still...another data point. I also like Code Analyzer / Mlint and have no desire to turn them off to improve Editor performance, as it was not necessary to do so previously.

I have also noticed, as Tobias has, that opening files can be really slow sometimes. However, I believe this problem was already present in R2012b.

Answer 6

[Scott]

Such a pity.

It's been a year and a half since I first asked for solutions to this problem. It only seems to get worse with each new release. It's made the Matlab editor virtually unusable. You would think the Matlab staff would make this the top priority. Or are they all flummoxed by this problem?

Does anyone else have experience with an alternate editor that plays nicely with Matlab?

Answer 7

[Andrew Drake]

put "exit" as the first line

[Rik]

Similar situation, similar answer as here. My response to the flag by John Williams (who flagged this as malicious) can be found there.