I've recently been attempting to update a large application from Labview 2014 32-bit to Labview 2023/4 32-bit. I initially had some problems moving directly to 2023 Q3 from 2014 so I decided to upgrade in 2 year steps which worked fine (recompilation and build) at each stage until I reached 2023 Q3 and 2024 Q1 (Note 2023 Q1 also worked fine).
Although the recompilation in both 2023 Q3 & 2024 Q1 was relatively painless, the build failed in an unusual way. After the initial "Initializing - this may take several minutes" which did indeed take several minutes, the dialog changed to "processing lvsound.dll" at which point the ram usage started to increase rapidly from approximately 2300MB to 3000MB followed by a "not enough memory" dialog box and then an app builder freeze. I decided then to remove all references to the lvsound.dll at re-attempted the build at which point it did the same thing but with the 'lvanlys.dll' and then 'lvwutil32.dll'. I've been using labview for many years and I don't remember seeing this processing of dlls in the build process before - is this new and if so why is it destroying my builds!?
Although the ram usage during the build process from 2014 to 2023 Q1 did increase, the peak was around 2400MB for my application and still well within limits prior to 2023 Q3 & 2024 Q1.
I've also been investigating the possibility of moving to 64-bit but this doesn't look trivial and I don't see this as a real solution. Any advice would be much appreciated!
Edit - I don't think it necessarily has anything to do with the dlls as I just attempted a build with shared libraries excluded which did the same thing - just a massive RAM bloat and then crash, I'm really not sure what to do.
