06-07-2023 03:52 AM
Hi,
I have to report an issue about this solution the High Resolution Relative Seconds VI putted in a loop can cause an Out of memory in a short time. That was why I have always inserted it in a case struct to make it start only when needed. Is there a better why to solve it?
Best Regards,
Zuc
06-07-2023 07:57 AM
Does it have to be the High resolution ? Try replacing Both by Tick count.
06-07-2023 08:33 AM
@Zuc_Lab wrote:
I have to report an issue about this solution the High Resolution Relative Seconds VI putted in a loop can cause an Out of memory in a short time. That was why I have always inserted it in a case struct to make it start only when needed. Is there a better why to solve it?
That really cannot happen unless you autoindex at the loop boundary and create an array of ticks, one per iteration, forever.
The high resolution relative seconds is quite lightweight and does not significantly contribute to the loop overhead. Of course it is only really necessary to do it once after the loop (using proper dataflow to enforce execution order) as shown above at the cost of slightly more diagram code.