LabVIEW
exe building makes small file
I was always amazed by the skills of the early chess programmers. It is hard to imagine that a fully functioning chess program can fit on a 4 bit microcontroller with 2k Rom and 80 bytes (160 nibbles) of ram. (yes 80, not 80k!)
@tvirag
No resolution really. I'm just redoing build until it succeeds. Sometimes do few manual retries, sometimes use Jenkins with file size post build checks and auto rebuilds as needed.
By the way - i'm using Labview 2018x32. Maybe switching to x64 or newer version of LV will help with that, haven't tried yet.
Have you monitored the memory usage during the build?
IIRC, 2GB is the (normal) limit for 32 bit applications. LabVIEW, 8000 VIs in memory, copies for the build maybe, additional resources in use, it could be a problem... LabVIEW keeps VI data in memory, so maybe this could cause the random factor?
I'd expect a hard "out of memory" crash, but who knows...
Search LabVIEW like a graph! 
Yes i've increased GDI limit, without it build crashes 100%. The point is that there is a problem which manifests in 144KB exe file after successful build. Logs also don't show any problems.
Have been monitoring memory all the way. Max memory usage goes to 3.2-3.4 GB depending on PC where build happens. We've tried it on about 10 different PCs and results are quire similar.
