Why does "IMAQ Create" time increase non-linearly with increasing buffers?

[BlueCheese]

The fix will be included in the fall round of updates (SP1/19.5), but currently these aren't available yet for download.

You will just need to update either Vision Acquisition or Vision Development Module to get the fix (installing either will update the affected component).

Eric

[BradC]

Hi

This problem has been fixed in the development environment, but it is not fixed in built exe files.

This is a real problem for my application, as the slowdown is so large that it's triggering a timeout in my code intended as an escape in the case

of abort. But it is being triggered normally in the exe. I really need to solve this compiler problem. I have tried setting the compiler to 10.

Are there any settings that can be changed to apply the same fix from the dev environment to the complier?

Example code is attached. I am using LV 2019 SP1

[BlueCheese]

The runtime path in the Vision DLLs that caused the issue is the same in both compiled LV executables and in the LV dev environment. Are you are you see this issue on the same system you are testing the development env on? If you deploy to a system with older Vision DLLs, I’d expect this problem to still exist, regardless of what version you compiled it with.

[BradC]

HI

I have tested it on two separate systems with the same result.

Please try and compile the code I attached and see if you see the same problem. I get a slowdown of a factor of 10 with the compiled version I attached.

Both systems are LV 2019 SP1 where the issue is solved in the dev env

Regards

Brad

[BlueCheese]

Hi Brad,

I reproduced this and filed this as bug 1182809. It appears that in a compiled LV app, the LV runtime uses a different search mode when accessing the refnum list than the one used in the development environment.

Eric

[BradC]

Thanks

Hopefully there is an easy workaround to change the search mode

Bradley