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

eeglabout of memory error

Hello,

I am receiving the following error message:

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

Error in fileparts (line 35)

elseif ~isrow(file)

I have already tried renaming as well as deleting the isrow.m fime in my eeglab folder with the Matlab folder. I have also tried removing the entire folder that contain the isrow.m file from the path but am still receiving the same error message.

*Thank you for any assistance*

Best Answer

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.

Related Solutions

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

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

Give the commands

restoredefaultpath
rehash toolboxcache
savepath

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 and unable to save pathdef.m

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

Related Question