Thanks! I can confirm the problem with your .t1 file. It happens on my PC too and looks like a bad allocation order when Zorro loads the historical data - as if a new area is allocated before the old one is freed. This exceeds the limit every time. This can be probably fixed and we'll do that with high priority before the next release.