03-07-2018 01:31 AM - edited 03-07-2018 01:35 AM
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.
03-08-2018 04:46 AM
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.