Engine.DisplayMessageBox versus CPU

[PragmaTest]

Hi,

I noticed that the Engine.DisplayMessageBox is CPU intensive for no reason (one core saturated).

As an example this method is used in the VI Display Error of both Simple and Full-Featured LabVIEW OI.

Sébastien

[PragmaTest]

Any thought of TestStand dev team ?

[Anand_Jain]

Hi, 

I am unable to reproduce this issue using TS 2021 in SeqEdit, LV 20.0 and LV-build executable (LV 20.0) . I have also verified that the code in the TestStand engine has not changed to impact behavior since TS 4.0. 

Couple of questions:

What version of TestStand and LabVIEW are you using? Are you able to reproduce this issue on multiple machines? 

Regards, 

Anand Jain

NI

[PragmaTest]

Hi,

I use TS 2020 and LV 2020.

The issue is very easy to reproduce by generating a fake error into the state machine of the simple TS OI.

With breakpoints I see my CPU going from 1% to 12% when the error message is displayed, then falling back to 1% afterwards.

Thanks