What causes the save command (in MATLAB) to fail?

We deploy a medium size application written in MATLAB and we allow the user to save their simulations settings and data. Inside the code, we are simply using the save command. The vast majority of the time it works fine, but occasionally the MAT file is corrupted and the project cannot be reloaded. I got a user last week complaining that this happens to him almost regularly. The user runs a 64-bit system and our deployed version is compiled for 32-bit. This problem is hard to reproduce and hard to guess what the problem could be. What causes the save command to fail and how could we control for this?

[Walter Roberson]

Are you using a Networked File System? If so then is it NFS based?

Answer 1

[Sachin Ganjare]

If data being stored is of complex nature & is stored with -ascii option, then according to matlab documentation:

"Saving complex data with the -ascii keyword causes the imaginary part of the data to be lost, as MATLAB cannot load nonnumeric data ('i')."

Hope this information helps!!!

Answer 2

[the cyclist]

It is conceivable to me that this is a version mismatch issue. Maybe look at the MAT-file save format under MATLAB --> Preferences --> General --> MAT-Files, and see if there are differences.

Also, certain classes cannot be saved to MAT file, such as database connection objects. Perhaps the issue has to do with the occasional presence of those?