Is TestStand Large Address Aware?

[pwaszkewitz]

Hi Doug,

thank you for the confirmation that this is most likely an access violation. I am not directly involved with the system, as soon as I have access, I will try to check that error with a debugger.

Thanks

Peter

[pwaszkewitz]

Norbert,

thank you for the explanation.

Actually, this happens inside a single TestStand step. The step calls an interpreter which in turn carries out an image processing in which the image is computed from raw data, then evaluated, and it is the evaluation that crashes on the original image handle and works fine on the copy.

Therefore, I am currently working from the assumption that a particular 3rd party DLL does some kind of garbage collecting and clears the memory in question away before we have finished using it.

Regards

Peter