Tick based backtesting crashing with Error #62081310

Created at 09 Mar 2020, 18:45
Subscribe
How’s your experience with the cTrader Platform?
Your feedback is crucial to cTrader's development. Please take a few seconds to share your opinion and help us improve your trading experience. Thanks!
SC

scotpip

Follow

Joined 24.07.2018

Tick based backtesting crashing with Error #62081310
09 Mar 2020, 18:45

Hi

Attempting to run a tick-based backtest across the full range of data available.

After running a few months of data the backtest crashes. Sometime this freezes the client, sometimes it stays responsive.

This is 100% repeatable.

The log shows the message: cBot crashed: Error #62081310

I've tried this using an empty bot that is doing zero processing, so the issue is not with my code.

I am running on a well resourced HP Workstation and there is a large margin of unused memory and CPU at the OS level.

I suspect you have an object in your code which is butting up against the CLR 2 gig max size?

I've hit this issue within my first 20 minutes of using Automate. I'm very much hoping to switch the the CTrader platform, but this is a demoralising introduction.

I've written my own bare-bones backtester in Java and it could push through 10 years of tick data much faster and without memory issues. It does raise concerns as to whether the backtester really is production ready?

@scotpip
Replies

PanagiotisCharalampous
10 Mar 2020, 08:27

Hi scotpip,

Can you please try cleaning your Backtesting Cache (C:\Users\UserAppData\Roaming\broker cTrader\BacktestingCache) and and let us know if it resolves the issue?

Best Regards,

Panagiotis 

Join us on Telegram

 

 

@PanagiotisCharalampous

scotpip
10 Mar 2020, 16:05

Thanks for the quick response.

Clearing the cache made no difference I'm afraid. Crashing after around 20 months, as before on 3 runs. I'm running the test on an empty bot for GBPUSD t1.

10/03/2020 13:16:41.356 | cBot crashed: Error #62081310

But I've noticed on each case the crash was at 10/10/2016 00:00:00. Maybe a data glitch? I'll try a different pair and report back - but the ticks are VERY slow to download from ICM, so may take some time.

It's not an OS-level resource issue. I have 90% of CPU and 60% of memory unused.

 

 

@scotpip

scotpip
10 Mar 2020, 16:41

RE:

Nope - crashed again at a similar but different date and time on EURUSD t1.

10/03/2020 14:39:28.082 | cBot crashed: Error #62081310
 

@scotpip

PanagiotisCharalampous
10 Mar 2020, 16:42

Hi scotpip,

Thanks, I managed to reproduce it. We will check.

Best Regards,

Panagiotis 

Join us on Telegram

@PanagiotisCharalampous

scotpip
17 Mar 2020, 18:51

PanagiotisCharalampous said:

Thanks, I managed to reproduce it. We will check

Any progress on this? Can't really commit to the platform while there's a bug that will limit my ability to backtest...

@scotpip

PanagiotisCharalampous
19 Mar 2020, 12:31

Hi scotpip,

We are working on this. It will be fixed in an upcoming update.

Best Regards,

Panagiotis 

Join us on Telegram

@PanagiotisCharalampous
Copyright © 2024 Spotware Systems Ltd. All rights reserved.
The services provided by Spotware Systems Ltd. are not available to citizens or residents of the USA. Neither is the information on our websites directed toward soliciting citizens or residents of the USA.