Error using save: Error closing file

Hey all,

An instance of a class is filled with a lot of data and than saved to my harddisk.

However, during saving, I get the following error: Error using save: Error closing file dummy.mat

I thought it had to do with a lack of memory, but I've monitored the process during saving and I never run out of RAM, and I know that I have plenty of space left on my harddisk.

Does anyone know what causes this error?

Any suggestions are much appreciated!

[Rafael Lopez Campos]

Hi, I had the same problem. I was working my script in a external device, so I fixed it moving my environment in the same device Matlab is installed.

Answer 1

[Jared]

Hi Bert,

I ran into the same error message a day or two ago with a struct filled with instances of classes that were similarly filled with lots of data. However, I could see in task manager that the memory use was in fact spiking.

The problem went away when I switched to version 7.3 format from version 7 (change file->preferences->general->MAT-Files or I think add flag '-v7.3' to save). This led me to believe that the memory problems might have had something to do with the form of compression done in mat files in version 7.

However, this does not solve another problem associated with save and load which might also cause some issues (it does for me). MATLAB uses lazy copying to conserve memory, i.e. A = B does not make a new copy of B until some part of A is later changed, e.g. perhaps A(end) = 1. Mat files appear to forget about all of these memory-saving relations, increasing both the size of the save files as well as the space required in memory once the save file is loaded.

Hope this helps! Jared

[Bert]

Hey Jared,

Indeed this turned out to be the problem. I figured this out a while ago but forgot to report it to the community.

I think it would be a valuable addition in the error message as a suggestion ('Maybe add -v7.3?'), because the user is pretty much left in the dark about the reasons of this error message.

[Jesse Salazar]

Also worked for me. No issues thus far with the lazy copying. Bert, do you anticipate issues with data integrity? Or simply with redundancy/memory? For my purposes, as long as there is no issue with data integrity, I should be okay. Thanks for your post,

-J

[Colin]

Great answer. I would have lost days without it! Thanks!

[Céldor]

Thanks for this answer. I had the same error and adding '-v7.3' solved the problem. Before, I though the problem would be somewhere else as it suggests network or HDD problems.

I also believe adding more explanatory error would save everybody's time.

[Scott Tuttle]

Many Thanks Jared! Using '-v7.3' on the save command fixed my case. I now made 7.3 the default in my preferences.

[Rosalyn Putland]

Thanks this fix worked perfectly!

[Hans Kramer]

Thanks man. Worked for me as well.

[Manuel Lera Ramírez]

Hello Jared,

Thank you so much for your response. Allowed me to save some data it had taken me a while to analyse.

[Mingli ZHU]

Tnanks, that helps

Answer 2

[Jonathan Pelham]

I have had a similar error message. This is a very old q&a. Does anyone know if the answer is still valid?

[Ingo Schalk-Schupp]

For me, this also did the trick. I was saving using the -v6 switch, and I got the error reproducibly. After I removed it, the error did not occur any longer.

Answer 3

[Zaki Mohzani]

Ran into this error today. That error message should be updated to reflect the new 'v7.3' option.

[Henrique Costa]

Now it is: save('myFile.mat','-v7.3','-nocompression');

[Henrique Costa]

or, if you want compression : save('myFile.mat','-v7.3');

[Adam Bruce]

This still works on 2020a. Thanks!