02-26-2010 03:01 PM
02-26-2010
03:56 PM
- last edited on
05-19-2025
04:24 PM
by
Content Cleaner
I believe the LabVIEW compile server is a 32-bit application and is limited to 2GB of address space (check out this MSDN document: http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx). There are flags you can modify to allow use of more memory and MSDN has documentation supporting this.
There is a LabVIEW Help document describing the process for increasing address space here: http://zone.ni.com/reference/en-XX/help/371361F-01/lvhowto/enable_lrg_ad_aware/
...And this particular issue of the LabVIEW Compile Server running out of memory has been documented here: http://digital.ni.com/public.nsf/allkb/F89C3D88819B8DE68625744800815537
02-26-2010 04:04 PM
In this instance, the application that is running out of memory is the Xilinx compiler, not the LabVIEW compile server. This isn't necessarily a limitation of the LabVIEW or Xilinx, but rather the Windows operating system. On 32-bit systems, Windows can allow 4 GB of virtual memory space per process. However, by default, this allocation is split up so the process gets 2 GB and the OS gets 2 GB. So, Windows is only allowing the Xilinx tools to access 2 GB of virtual memory.
The process that Bob linked basically tells Windows to only take 1 GB for itself and allow the other 3 GB to be used by applications, which should help your compiles to complete.