01-21-2025 06:28 PM
I have several Windows apps that run "unattended" via a startup shortcut. Each of these apps use a common framework that launches via a VI that is intended to be hidden immediately after startup as it mostly just contains LVClass constants for dependencies to inject.
The issue is that as the common framework has grown and takes longer to load into memory, the node to hide the launcher intermittently does nothing. It seems to be a race condition as the computer is loading things after the user logs in (so CPU usage is high as is disk throughput). I've seen this on VMs and PXIs.
The actual LabVIEW app is actually doing nothing at the time the invoke node is called as it is called sequentially before any additional threads spawn. No plugins or anything so theoretically all the code is in memory already -- this happens for built Windows executables with several DLL dependencies (DDS toolkit, SQLite).
The code that used to work consistently but now ~randomly does not hide the launcher:
In debugging this I tried this approach but the FP.State node returns "Hidden" and no error on the 1st iteration despite the launcher window being left visible.
So, has anyone seen this? I've tried to replicate with test code but I can only make it happen with a proprietary framework that is difficult to share... This happens with 2021 SP1 RTE and 2024 Q3.