Bug In Builder LV2012 - VI reported BAD when building - Need a workaround ASAP

[DanyAllard]

Hello,

I currently have a problem with building and application. The Builder report a VI to be in BAD state when saving the VI near the end of the building process. I got this problem a couple of time, and to resolve it I need to clear the Compiled Object Cash and recompile all the VI by clicking CTRL-SHIFT RUN. Save the VI's and rebuild.

But now I'm getting this error all the time:

I post this problem here because I didn't get success with the normal support and I need to escalate this problem as quick as possible to get proper support.

Someone get similar problem with LabVIEW 2012?

[GregFreeman]

Sometimes when weird stuff liek this happens, I go with a full save and close of and reboot. Have you tried this yet?

[DanyAllard]

---

@for(imstuck) wrote:

Sometimes when weird stuff liek this happens, I go with a full save and close of and reboot. Have you tried this yet?

---

Yes same result... Some bug appen always when you have the pressure to deliver somthing by next day 😞

[GregFreeman]

I will do some digging to see what I can come up with, but I'm pretty sure it won't be anymore than what you've already tried. I will say I have had some issues with builds in 2012, moreso than usual.

Have you tried to enable debugging? I've seen that sometimes helps, although it bloats your exe. Are you using LVOOP?

[DanyAllard]

I found a workaround:

I made a VI that include all VIs of my project to be sure that all my VI's are in memory and not broken. I press CTRL-SHIFT RUN on that AllVI.vi and I got broken VI's telling that there is not enough memory to compile VI.

After a couple of reboot, retry of the CTRL-SHIFT RUN, I finally got a clean arrow. I saved all the VI's and made a build and I finally got something working.

So that a pain. It's a really annoying bug that make me mad about LabVIEW.

[GregFreeman]

can you reproduce consistently?! If so send it to NI. I know this issue has plagued many people.

[gregstoll]

I'm just guessing here, but one thing that might help is lowering the compiler slider (Tools->Options->Environment, at the bottom).  It might also help to turn off stripping typedefs, if you have that turned on in your build specification.

[Thoric]

Just a thought: if you're running out of memory loading all the VIs into memory at once for a full recompile, then is the Application Builder running out of memory when creating your build? Have you tracked the memory usage of you PC whilst compiling to see if you're running short?

[DanyAllard]

---

@gregstoll wrote:

I'm just guessing here, but one thing that might help is lowering the compiler slider (Tools->Options->Environment, at the bottom).  It might also help to turn off stripping typedefs, if you have that turned on in your build specification.

---

That interesting, but I tougth that the compiler slider is just to improve compile time at edit time. Is it supposed to affect compile of a EXE build?

For typedefs striping is already at off.

[DanyAllard]

---

@Thoric wrote:

Just a thought: if you're running out of memory loading all the VIs into memory at once for a full recompile, then is the Application Builder running out of memory when creating your build? Have you tracked the memory usage of you PC whilst compiling to see if you're running short?

---

When I make a build the memory usage of LabVIEW top at ~900M.  and my VM has 3G of RAM. But the build don't report memory issue.