LabVIEW hangs while building exe

[t.d.b]

I am using labview 2014. Recently I have started encountering a problem of labview hanging while building the exe. The Build status proceeds to compiling without any problem. Then it proceeds to saving vis. The green progress bar file up to the end. The Explore and Done button get enabled, Cancel button is disabled. But the status still says saving some vi.

At the path where the exe is supposed to get built, I get a Data folder and an application.exe folder. There is no actual exe. LabVIEW is also hanged. I have to kill it from Windows task manager to be able to do anything. 

If i keep trying to build the exe, it finally gets built after 5-6 attempts. 

Any suggestions as to what the issue might be?

[altenbach]

Are you running some antivirus or other security software? Part of building an exe is modifying an existing exe by including more components and this might look suspicious to some tools (For a dumb antivirus, this looks similar to a virus modifying an executable, even though it is legitimate).

Hard to tell what's going on. Also, do you have sufficient disk space? Did you check the disk for errors? Did you do a "right-click...clean" on the build spec.

[t.d.b]

It is not an antivirus issue. I can build exe from other projects. It is one particular project where I am facing this issue. 

There is enough space on hard disk. Cleaning the build spec also did not help. 

The program runs properly when run from code. So there is no broken vi either. 

Is there some LabVIEW internal log where I can check if any particular vi or library is causing this error?

[billko]

I've seen LabVIEW have issues when building an executable containing VIs with huge memory footprints, like front panels with controls that contain lots of data, or constants on the block diagram.  You can see this when it's compiling by watching LabVIEW suddenly start eating up huge chunks of memory when creating the executable.  If you're lucky, LabVIEW manages to squeak by and the memory consumption drops back to normal.

[t.d.b]

Any suggestions on how to get by this issue?

[billko]

Besides trying to reduce the memory footprint?  I think if you restart LabVIEW and build before you do anything (after loading the project, of course), you stand a better chance of succeeding.