Problem building an applicatio

[AntonBolander]

Hi!

I have a quiet large VI which I would like to build an application for.  I have done this several times before (with other VIs) but when I trying to build this one the building proces get stuck when processing a VI, the RAM-raises and the building and LabView crashes (saying not enough memory). The VI for which the building gets stuck on differs all the time. I guess I can accept that if you have a large program and the RAM is not just enough to build the appplication the program will shut down but it seems strange that the buidling get stuck on different VIs and that the RAM raises so much for only one VI.

Someone have any idea how to solve this?

Inclusion type: Include if referenced

Using LabVIEW 2015 SP1, 32-bit

 /Anton

[GerdW]

Hi Anton,

I have a quiet large VI which I would like to build an application for.

Create smaller VIs, use more subVIs…

any idea how to solve this?

Create "software modules" you can call using VIServer (or by CLFN) from your executable. Create those modules using PPLibs or DLLs. In the end your MainVI should get smaller and starts to load needed software parts later…

[AntonBolander]

Well, the main Vi consiste of several small VIs. 

Would using a VIServer work when I (which I not mentioned) will build an installer?

[GerdW]

Hi Anton,

yes, sure.

[AntonBolander]

I  cant figure out how this work.. I need to redo my hole application right?

I came across this: http://digital.ni.com/public.nsf/allkb/CBEBDC184655FC8C8625724A00050854 

I thought that might be worth trying, however how do you know which VIs that are dynamic and 1st level?

[Bob_Schor]

Did you notice that the article you references was to building an executable on a 32-bit OS?  You report you are running LabVIEW 32-bit (which many of us run), but are you running on 32-bit Windows, as well?  [I'd venture to guess that at least 90% of LabVIEW users run on 64-bit Windows, even if running 32-bit LabVIEW -- I certainly do!].

Why is your application so large?  Are you working with really big data structures?  Are you writing very memory-inefficient code?  Have you looked at your VIs to see how much memory they consume?

If you want more specific suggestions, you may need to post (some of) your code (as VIs -- posting pictures of code won't help us help you) ...

Bob Schor