LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

ProcessSystemEvents() slowing down

I tried your example as well, but cannot confirm your observation the same as Wolfgang.

Win 10 64-bit, CVI2015SP1f1.

Memory footprint (2.3 MB) does not change in the first 3 minutes both in debug and release. Elapsed time is constant in 1-2 msec regardless the mouse position.

 

I wonder whether the situation changes a little if you put out 'static' keyword on clock_t variables.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 21 of 22
(593 Views)

I confirmed the issue on 5 computers at my company.

All 5 are running win10 64.

4 of them are running Labwindows/CVI base 2017.

1 of them only has CVIRTE 2017.

 

It looks like it's something related to how our computers are configured, so I will let the IT guys manage this directly with NI.

 

Moreover, I think I have found one problem in my program which is partly responsible of the memory usage increase I see in my full program.

I'll start another thread for this.

 

0 Kudos
Message 22 of 22
(579 Views)