MATLAB: Out of memory and unable to save pathdef.m

out of memorypathdef.m

Hi all,

I've reinstalled Matlab2017b and now I'm running into problems that I never had before.

when I try to save pathdef.m using the GUI I always get a messsage saying I don't have write access to save in the selected folder (screenshot attached). The problem is that this happens in any folder I try (even in an external disk). When I try to save via command line this gets me to the other problem that I'm getting:
When trying to open/run scripts I get this error:

Out of memory. The likely cause is an infinite recursion within the program.

Error in fileparts (line 37)

elseif ~isrow(file)

This happens even if I try to load a script from my current folder by double clicking.

I've never had these issues before.

Any feedback would be very much appreciated!

Andreia

Best Answer

It sounds as if you accidentally introduced a third party isrow.m

Give the commands

restoredefaultpath
rehash toolboxcache
savepath

Related Solutions

MATLAB: Out of memory. The likely cause is an infinite recursion within the program.

You, or some code you've downloaded is shadowing the isrow.m function of matlab.

Hopefully, the isrow.m you've deleted is not the matlab one (otherwise, you'll have to reinstall matlab I'm afraid) but the shadowing one.

Two toolboxes that have been shown to shadow essential built-in matlab functions:

The biosig plugin of eeglab
The fieldtrip toolbox (whatever that is)

That latter one in particular caused exactly the error reported here.

MATLAB: Matlab doesn’t “Pause on Error” till Infinite recursion

Try setting a breakpoint on line 237 of wPLI_openfield. When MATLAB reaches that point, it will enter debug mode and the prompt will change to K>>. At this point, check that the fileparts and isrow functions that are being called are the ones written by MathWorks.

which -all fileparts
which -all isrow

This will check if there are fileparts or isrow functions in a directory that wPLI_openfield (or something called before wPLI_openfield) changes to with cd or adds to the path with addpath (but that the code normally changes away from or removes from the path before returning to the Command Prompt) and so were not "visible" to MATLAB when you checked before.

If that doesn't show anything, Walter may still be correct that there is a third-party toolbox interfering. To check this, can you show the list of products displayed when you execute the ver function? That's not foolproof (not all third-party toolboxes do what's needed to show up in ver, but it might show something that we've seen before and recognize as a potential cause.

Best Answer

Related Solutions

MATLAB: Out of memory. The likely cause is an infinite recursion within the program.

MATLAB: Matlab doesn’t “Pause on Error” till Infinite recursion

Related Question