LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 2 - full memory


Hi!!

I have a critical problem, when trying to build a standalone application, I get the follwing error :

Error 2 occurred at Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->
AB_Build_Invoke.vi.ProxyCaller

Possible reason(s):

LabVIEW:  Memory is full.
=========================
NI-488:  No Listeners on the GPIB.

Method Name: Save:Target Instrument


This is my first time building an application after upgrading to LV 8.5, I have lots of memory free.
My first guess is that this is a upgrade to 8.5 issue, since I have never had this error message before when running 8.2.1.

What may I do to be able to give my costumers a new release.

Best regards,
A
0 Kudos
Message 1 of 5
(5,023 Views)
Hi
This error is caused by a limitation in the memory space available to a single process in a 32-bit operating system. This limitation has actually been improved in LabVIEW 8.5 by dividing the task into more processes. You can either refactor your code, or you can change the memory configuration in Windows.
0 Kudos
Message 2 of 5
(4,990 Views)
Hello!!
 
I actually solve a part of the problem.
 
Two included project files were suffering with conflicts concering file path - when renaming the two vi's I was able to build an application again,  no error about full memory.
 
I would rather like to fix the conflict than to rename the vi's since the vis are referred to in serveral places, in addition, even if I delete the two project files and include them again from the correct file path, they still are marked with 'conflict'.
 
When I try to solve the the conflict by picking the file path which I would like to use, I am not able to, because when choosing "save"  I get a NEW error : "LabVIEW: Memory is full. Labview save error code 10:default data space"
 
The strange thing is that I am able to:
1) save single vi after making changes 
 
2) save the whole project
 
I have read the document you included in the reply and if you have other comments in addition I would be very glad!!!
 
Best regards,
 
A
0 Kudos
Message 3 of 5
(4,989 Views)
Do the two VI’s have the same name? That would certainly cause problems in LabVIEW. You can’t have several files with the same name in a project. If you insist on doing that I have read that putting one of the files in a library is the way to go.
0 Kudos
Message 4 of 5
(4,982 Views)
 
 
Hello!!!
 
I do not want to include 2 vis in a project with similar name, you misunderstood !!
 
The conflict was created because I had 2 different paths with 2 similar vis, and even if the previous path had been deleted a long time ago and the correct path was set, the project manager reported a conflict. When I was running LV 8.2.1 this conflict was never visible.
 
I solve the situation with a rename where the rename function update the rename in all VIs which the vi is used. Then the FULL MEMORY error is solved.
 
Anita.  
0 Kudos
Message 5 of 5
(4,979 Views)