"memory full" error while saving. Can I recover VI?

[massimarini]

While I was saving a VI, a "memory full" error is occurred. I tried to save again and there was no other error. Now, when I try to open the VI, the error dialog: "Labview load error code 16:Could not load data space link information" appear. It seems that I lost all my work, but there is a method to recovery the VI?

Thanks to all for any suggestion.

Max

[mikeporter]

To be short and to the point: You're hosed....

You'll need to rebuild the VI.

Mike...

[mikeporter]

Since I sent my first post I had another thought that might provide a little hope--still not very much, but a little. Go to your computer's temp directory and you should find some vi files hanging around. LV keeps copies if the files it has open in the temp directory. Normally LV cleans up these files when it quits but seeing as how your editing session didn't quit normally, you might be able to find a pre-crash version of your code in there somewhere. No guarantees, but it's a possibility.

Mike...

[tst]

And, of course, the usual, very-annoying-but-very-true, advice - ALWAYS backup.

As a frequent backup I have a directory into which I copy the files I'm working on at the end of each day (or, if I change a lot, in the middle of the day as well). Less frequent backups include other computers and multiple CDs, stored in different places.

[massimarini]

Hi Mike,
thanks a lot for your replay. I tried your suggestion, but I didn't find any VI file in the temp directory. Now, I started to rebuild my VI...and every time I save it I make a backup copy, just to be sure!!

Only another question. My computer has 1GB RAM and I seen  in windows task manager,  after the memory problem,  that LV used about 400MB of memory and there was still 300MB of free RAM(the other RAM was used by .othr programs). How is possible that I had a "memory full" error? More over, why LV use so much memory if only 2 VI are opened? This questions are only to avoid that I will not have again this kind of problems.

Thanks again for your help

Max

[mikeporter]

The problem with errors like this is that very often the software as it is dying is trying to figure out what happened, and very often the answer comes out wrong. In terms of why you still seemed to have memory left, it could have been a transient condition that didn't last long enough for task manager to see it.

As I have said before, remember the maxim: "Stuff Happens".

Saving often, not using LLBs and running good background backup software can save you from a world of hurt. In situations like this I also look at it philisophically in that it seems like the code I rebuild is always better than what I created the first time.

Hmmmm.... Maybe I need to change my maxim to: "Stuff Happens--and that's not necessarily a bad thing..."

Mike...

[Ben]

"Only another question. My computer has 1GB RAM and I seen  in windows task manager,  after the memory problem,  that LV used about 400MB of memory and there was still 300MB of free RAM(the other RAM was used by .othr programs).

"

Memory full is the erro returned if LV attempts to allocate memory and it can not. When allocating, the memory MUST BE CONTIGUOUS!

Warning: The following may change version to version and is based on my observations.

As i understand it, LV will enusre a buffer is larege enough to handle new data before the data is added. If the buffer needs expanded. LV will DOUBLE (Note: My understading, NOT known to be true) the size of the buffer. Under this scheme, if your buffer was 200MB and needed expanded, LV would have to acquire a block of 400MB from the OS.

Just my understading....

If someone knows better, please chime in.

Trying to help,

Ben