"Build" operation to generate startup.rtexe causes memory release problem on host machine

[Chris_12345]

I have a LV2012 project that contains OOP and many cRIO chassis. Every time that I do a "Build" operation to generate a startup.rtexe file, the Windows task manager shows the memory allocated to LabVIEW increases significantly. After doing several Build operations, my machine runs out of memory and I need to re-open LabVIEW and the project (a time-consuming task).

What can I do to avoid this memory problem? LabVIEW doesn't seem to be releasing memory used for the Build operations.

Thank you for any help you can offer.

[JaymeW]

Hi Chris, 

A few questions that might help sort out what's going on here:  What operating system are you using?  How big are the individual builds?  Are you using auto-populating folders in your project? 

[Chris_12345]

>What operating system are you using? Windows XP, with 4 Gig of RAM and 4 processors.

>How big are the individual builds? Each of the rtexe files is about 5.8 Mbytes.

>Are you using auto-populating folders in your project? No.

I'm not running any VIs, just manually and sequentially doing Build operations for my cRIO chassis. LabVIEW grabs more memory upon each build, and doesn't let go.

Out of curiousity, I did try to run a simple VI containing just a Request Deallocation (wired with a True), to see if it would get LabVIEW to stop hanging onto memory, but no luck. I even tried adjusting the priority of the LabVIEW process and which processors it is running on, to see if that would jiggle memory loose, to no avail.

[JaymeW]

Hi Chris,

If you close and re-open the project (not LabVIEW) before your computer runs out of memory, does that release the memory or do you have to close the development system as well?