Memory is full during "Save As" of LabVIEW 8.5 project

[LV_Pro]

Good Morning All,

     Have run into a weird issue while trying to rename a LabVIEW 8.5 project. I've got two projects that ended up having the same names (one by me, one by another engineer). I want to open both at the same time, so I figured I'd open the one and do a "save as", or a "rename". The first time it started processing, doing file loads, and then hung looking for a sub-vi, with the search address pointing to the .llb in the LV 8.5 directory where I manually located it. Once that was resolved, and the original project saved I tried again. This time it did a bunch of loading and then gave me an error box with the message:  "LabVIEW:  Memory is full.  Cannot save project 'original project name.lvproj'" This isn't a big project, the machine is a new HP Compaq dual core 2.8GHz with 1.5Gb of ram, so I don't really think that it should be generating anything that big. This happens with either a "save as" or "rename". I ended up just changing the names of the .lvproj .aliases files to the one I needed and it seems to load ok, but it would be nice to understand what is happening here.

[Johnnymysto]

I'm having the very same problem.  Just now, I tried to do a Save As with a project, and I wanted to save it under a different name.  LabVIEW showed a little box that looked like it was writing lots of different pieces of information, then finally popped up the "LabVIEW: Memory is full.  Cannot save project."

My computer is also nowhere near its memory capacity, so I'm also confused why I'm getting this error.

Thanks,
Eric

[eek]

This is interesting behavior, since NI actually ensured that you would now have the ability to Save As and Rename a project with the release of LV 8.5. I've tried this several times and have not encountered the behavior of which you speak.

What kind of files are contained within your projects?

Are they saved on the network perhaps?

Have you been able to reproduce this on with the same project on another computer by chance?

Hopefully we can get to the bottom of this.

Cheers,

Emilie K. | National Instruments

[LV_Pro]

I haven't had an opportunity to try it on another machine, don't have one with 8.5 installed that is available (I'm the "early adopter" for this customer, due to the nature of our project). I will add that the project is using LabVIEW Real Time 8.5 if that adds anything important to the mix. Nothing installed on a network drive, no Config Management software implemented (yet), a handful of shared variables on the RT part for communication between processes on the RT (between the deterministic code, running on one core, and the non-deterministic.)

Message Edited by LV_Pro on 10-15-2007 07:53 PM

[eek]

Well rather than trying this on another computer, let's try a simple project, sans shared variables, etc. Can you open an empty project, save it under one name and then do Save As to save another copy/change the name? Let's start simple and see if we can reproduce the error by building up from there.

Cheers,
Emilie K.

[JeffBoettcher]

Another thing that might be interesting would be copying just the project file by itself to a different location where it can't find any of its subVIs, and see if you still reproduce this error in that situation.  If so, perhaps you might be able to send us just the project file (posted here or via support if posting it publicly would be bad) for us to reproduce this here.  Seems likely it might require more than this, but it would be nice if that was all it took.  Same goes for you Eric...  If either of you can post part or all of your project where you see this issue, it would be very helpful in us being able to reproduce it.  While seeing if you can reproduce the problem with a new project is a good idea too, I'm pretty sure we tested that.  😉

[Logan_081]

Hi to all,

There's now availbale a KB about this issue

http://digital.ni.com/public.nsf/allkb/FAC7D18C4072945E862573D9003F8DBA?OpenDocument

Cheers

[pbuerki]

I am having the same issue. Unfortunately, dragging the files from one project window to the other does not work. Also existing builds cannot be transfered to the new project. Please advise.

Thanks.

Peter

[iZACHdx]

Hello,

Exactly what doesn't work when dragging from one project window to another? Existing builds cannot be transferred and that is expected. Any build specifications would have to be recreated.

-Zach

[pbuerki]

Hi,

Thanks for getting back to me.

I get the crossed through black circle (se attachment), and releasing the mouse button does not copy the file. I am using WinXP SP3.

I understand that any builds need to be recreated, which is apain since one cannot have two builds open at the same time, I would need to print out all pages of one build and then enter the information from paper into the recreated build. Thanks.

Peter