LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

compile error: out of memory exception caught in llvm gencode

For some reasons, I got an error message " COMPILE ERROR: out of memory exception caught in llvm gencode" when I use LabView 2010. This exact VI is running well in LabView 2009 and 2009 SP1, except that it takes almost 30 minutes to save or compile (it is about 2Mbyte).So, I do not know if it is the size of the VI problem ???  Is there any one got the same problem ??

 

 

I could notattach the VI since it is intentionally used for military program.

 

My system is,

 

Window XP

3 Gbyte RAM, 2.2 GHz

LabView 2010 Professional

 

 

 

 

0 Kudos
Message 1 of 28
(7,517 Views)

Hi Intania,

 

I have a couple of things for you to try:

 

1.) Can you place this VI (and any Sub VIs that you created that are used by this VI) in a folder and mass compile that folder in LabVIEW 2010? It could take a very long time to compile so please do this when you have an extended period of time to let it run.

2.) If you experience a crash during the mass compile, start the mass compile over again.

3.) If possible, try to mass compile your VI on a 64-bit operating system running LabVIEW 2010 32-bit. The reason for this is because LabVIEW 2010 32-bit is large address aware and will make use of up to 4GB of memory on a 64-bit operating system as opposed to 2GB that it utilize on a 32-bit operating system.

 

Also, when you say that it takes almost 30 minutes to save or compile, that is in LabVIEW 2009 (SP1), right?

 

Aaron P

National Instruments

Applications Engineer

http://www.ni.com/support

0 Kudos
Message 2 of 28
(7,487 Views)

Hi Intania,

 

Also, can you tell me the size of the top level VI's Block Diagram Objects? You can find this by going to File»VI Properties»Memory Usage. Thanks!

 

Aaron P

National Instruments

Applications Engineer

http://www.ni.com/support

0 Kudos
Message 3 of 28
(7,483 Views)

hi all,

 

i have the same error during the compilation after 1hour : "Compiler error : Report this problem to National Instuments tech support out of memory exception caught in llvm gencode"

i tried mass compile, it was a succes. but the construction crashed.

 

Best regards

XP 2Gb 2.41GHz

0 Kudos
Message 4 of 28
(7,457 Views)

I also have the same issue, are there any plans to try and reduce the memory requierements of LV 2010?

 

Keith Edmonds

0 Kudos
Message 5 of 28
(7,406 Views)

I do not have either computer operating with 64-bit environment at work or any faster computer. So, what I am doing right now is going back to  LabVIEW 2009.

 

The main VI has the memory usage of

 

Front Panel Objects: 1119.2K

Block Diagram Objects: 12587.6K

Code: 1753.9K

Data: 705.4K

Total: ~16166.1K

 

Total VI SIze on Disk: ~2144.2K

0 Kudos
Message 6 of 28
(7,402 Views)

Hi,

 

I have exactly the same problem:

My VI, which worked well under LV2009, now with LV2010 needs an huge amount of memory and ends up with the "memory exception cought". And yes, the System (WinXP) runs really out of memory within a few minutes.

If i take the old version of my VI and save it, then no errors and no memeory-exception occur. The crashed one could not be recovered with the mass-compile - trick.

I observed this on 2 different computers (both newest XP).

System1: 800MB ram+ 800MB cache;

System2: 2GB and 3GB.

VI: frontpanel 360K,  block diagramm 6800K,  code 2300K, data 670K,  sum 10.000K. But yes, lots of sub-vi-s.

 

Thanks for any hints!

Greets,

Uli

0 Kudos
Message 7 of 28
(7,276 Views)

I got the same problem recently. There was no problem when mass compiling but when you build the executable, that's another story, first half was smooth as a butter, but the second half, the process seem stop and then the window stop showing our vi and show "compiling" instead, and the error showed. This is new for me because I didn't get this kind of problem back in LabVIEW 2009. So we hope we get some solution soon because I need to deploy the system worldwide. Thank you for your attention.

0 Kudos
Message 8 of 28
(7,175 Views)

Hi All,

 

I resolved my problem. i added in the boot.ini the start up switch "/3GB" and now it works !

 

0 Kudos
Message 9 of 28
(7,165 Views)

Hi All,

 

I resolved my problem. i added in the boot.ini the start up switch "/3GB" and now it works !

 

0 Kudos
Message 10 of 28
(7,164 Views)