Application builder appears to complete but does not create executable

[fabric]

I'm working on a large project (~5000 VIs, LV2011 SP1, Win7 32bit) and have recently starting having issues with the Application Builder. This follows after 3-4 years of successful builds on this project...

When I attempt to build my top-level application the following happens:

1. "Build status" window opens as normal and starts processing my files:

2. Eventually the progress bar reaches approximately half way and the message changes to "Compiling...":

3. Next, the progress bar suddenly jumps to the end and the message changes to "Saving...". Also, the "Done" button becomes active as though the build has completed. The window stays like this forever. Notes about this dialog:

• The "Explore" and "Help" buttons work normally in this state. 
• If I press the "Done" button (or close the window with the red "X") then the window closes but Labview hangs. The only way out from here is to kill the process in Task Manager.

4. If I browse to my build folder then I see that the temporary build files are still sitting there, i.e. the builder has failed to create my exe...

When I enable logging I see that all files appear to be successfully processed (by comparing with a previous successful build log), but the log stops BEFORE writing the "[Output File Version]" section... 

Anyway - I'm in the process of rolling back a large number of small changes to see if I can isolate which of my code changes caused this issue.

Does anyone out there know what might cause the application builder to get as far as it does, thinking that it is done (even though it is not)?

Thanks for any ideas...

[JÞB]

Hmmm...

I'm suspicious.  there was a app builder bug "Fix" in 2011SP1 for builds sometimes unsuccessful.  A few things come to mind to try.

Retry the build.

Clean the build and retry

delete the destination directory manually and retry.

Then rollback and see if you did it.

[fabric · Accepted solution]

Well - I eventually managed to isolate the issue... Corrupt code is attached!

The attached code is a stripped down version of a dialog that is used in my project. The issue turned out to be related to the radio control inside the tab control:

• If you open the library and then attempt to REMOVE the two private controls from the library (simultaneously), then you are greeted with the crash report below. NOTE: Removing the private items one-at-a-time does not cause the crash! (weird...) 
• The same crash occurs if you try to rename the library

The solution:

• The inclusion of this library in my project was causing my application build to fail every time.
• Given that the report mentions "RadioClust.cpp", I made the incredible leap that the issue was connected with the radio control... so I simply disconnected all instances of that control from their typedef. That seems to have fixed it!

ASIDE: I have not checked whether including this library in another application will cause its build to fail too... Something to try on a rainy day!