compile error: out of memory exception caught in llvm gencode

[hex]

I'm not sure if I catch your method right, would you kind enough to elaborate your method? Thank you.

[Tanya_V]

The boot.ini file is a Windows file. Here's a link to a document that will show you how to change the virtual memory limits on Windows XP and Vista:

Extending Virtual Memory Usage for 32-bit Windows.

Let me know if this works in your case.

[hex]

Hello all,

This method also not working in my case, in the middle of constructing the executable, the process stopped and show the same error. Let me explain further about the post error. After the error showed, the LabVIEW is not clickable, so I have to force-close it using Windows Task Manager, I believe you who have the same error will get the same symptom.

After I restart my LabVIEW, I got some window popped up (see attachment Post Error window.png). In my code I have some "relics from the past" called state machine loop, That was created using state machine toolkit back in LabVIEW 7.x. So, my next step, which is I hope it's fruitfull, I'm going to change all the state machine loop inside my code.I'm afraid LV2010 cannot read that portion any longer, unlike LV2009.

One of the evidencet is the "Integer to Enum" icon in my code (belong to State Machine Toolkit) is weird/destroyed/missing (see attachment "weird icon.png"). If you guys have some alternative, please do share. I want to solve this problem before I downgrade to LV2009.

Thank you.

[loetknecht]

Good morning,

i can confirm having seen the post error once, too.

Also my main vi was created originally under Labview 5 (and grew through 7, 8.6, 2009 and now 2010).

Maybe that's a hint for the developers? How can we check for "obsolete" code?

Meanwhile one computer is supplied with more memory, there the memory consumption goes up to 2.~ GB, then heavy CPU load (~5 minutes!) then memory consumption dropps back to 1.7 and vi is running.

Please...?

[hex]

Dear all,

New finding, it appears that my previous statement is not accurate.

I can build executable file from vi (see attachment) smoothly. The vi's source version is 7.1 and coded using the same state machine/state diagram toolkit that I was using which is an obsolete (see vi properties), with this, I'm not sure whether "obsolete code" is the reason that caused error in .exe construction.

The real problem may be hidden somewhere else.

Thank you for your attention.

[loetknecht]

New observation here:

virtual computer equipped with 1G of "RAM". Vi consumes all CPU and all Memory, "save" or "mass compile" crashes after memory completely full (~4 Min).

Same(!) virtual computer equipped with 1.5GB. Vi consumes all CPU and nearly all Memory; but is, after 9 minutes, sucessfull in saving / mass compiling.

The amount of ("real") RAM in the (virtual) machine was the one and only difference. I have screenshots of cpu/mem consumption progress, if for somebody of any use.

Please, NI, .....

[BTreece]

It looks like you are seeing the heart of the issue.  When you run out of memory, LabVIEW crashes.  When you allocate more memory, LabVIEW successfully compiles.  I would suggest that you do not run your virtual machine with less than 1.5 GB of RAM.  

Brandon Treece

Applications Engineer

National Instruments

[loetknecht]

Hm, for me, the "heart" is more: why does this VI use so much memory. With Labview 2009 it did definitely not, compiling was successfull in less than a few 10 seconds. Besides: since the host computer does not have more memory (and my other real ones don't either), i cannot spend more virtual memory. The question is still: how to find out *what* exactly in Labview uses this much memory and *why* - and finally how to stop that?

PS: Funny, yesterday the vi compiled fast and with using less than 300MB of memory. Once. Second time as before again.

[d.mcandrew]

Tanya, I am getting this same error when I try to open a VI in LV2010. It opens fine in LV8.6. I have extended my virtual memory usage to 3GB following the instructions on your link (thanks!) but the issue is still there. Now my total memory usage just goes to >3GB before the error happens. (Labview.exe is using about 2.6GB) I tried increasing the virtual memory further but still get the same error message.

Also, after the error message the VI does open with a broken arrow but if I try to modify and save, LV crashes.

Thanks,

Dave

[BTreece]

The reason that the run arrow is broken is because VI has not completely compiled.  Take a look at this KnowledgeBase article that explains more about what is happening.  You can try intentionally breaking one of your subVIs while you are editing.  If you have a broken run arrow, LabVIEW will not try to compile when you hit save, allowing you to continue working.

Brandon Treece

Applications Engineer

National Instruments