Yes, my script uses probably too much memory for a single process.
If I split the backtest into 2 parts (25 assets per run) it works.
But I think that there is also a memory garbage collection problem in ZT that you could correct:

if in the original script (with 50 assets) I use the following:
set(PARAMETERS+TESTNOW+PLOTNOW);
it shows the error immediatly when it start the test phase;

if in the same script I use:
set(PARAMETERS+PLOTNOW);
it complete the train. If then I close ZT and then I start it again and select "Test": It complete the Test correctly!

This means that if at the end of the train phase you call a garbage collection routine (but i don't know if you have it in C) you could probably resolve this problem.

thanks

I got similar problem but I did not need to close the zorro. I put away the PLOTNOW and TESTNOW. When the train was completed, I clicked on test and then it was ok.

yes... and as I am not the only one that is reporting this problem I think we have a bug to resolve.

Jcl: do you think we can resolve it?
thanks

I can not confirm a garbage collection issue. And what you're describing is memory fragmentation, not garbage collection. But if you think something is wrong with executing your script, please send it to support. We'll look into it.

Giorm: thanks for the script. We'll looked into its memory allocation, but could not confirm a garbage collection issue. The behavior is what you described: TESTNOW gave a memory fragmentation error since it had to allocate large memory areas. Due to the previous training run, there was not enough contiguous memory for them. Normally you must then reduce memory consumption per script, but sometimes it also helps just to restart Zorro. This will free all memory allocated by the script. The end of the training run only frees memory specific for the training.

You're at the border of available memory and thus get those effects.

Jcl, thanks for the analysis.
So, if there is not any solution, I will divide the train task on different steps.

A new beta version, 1.41.9, was uploaded today. This is the candidate for the 1.42 release. Aside from the new user panels, 1.42 supports better strategy debugging by single stepping into bars and loops.

I am having difficulties with the control panel for the Download.x file. The [Load M1 Data] and [Load Tick Data] blue buttons are unresponsive. The other blue buttons respond as described in the manual.

This could be because I tried to connect to the broker on a weekend. But I pinged the broker's server and got a response. I would have expected an error message if this was the issue, however I get no response at all when clicking these buttons.

I'll try again on Monday and see if there is any change.