cTrader crash when running cBots

ncel01
28 Nov 2022, 14:04 ( Updated at: 21 Dec 2023, 09:23 )

RE:

Hello,

Is there any update on this issue?

Thanks.

ncel01 said:

Hello Team,

I've noticed multiple times that, after some hours running cBots, cTrader crashes unexpectedly.

I am now using Windows 11 Pro, however, this issue is not recent and it already happened before, when using my previous PC (Windows 10).

The RAM usage by cTrader looks a bit high, however, it is still acceptable and it looks stable while the app is running the bots:

Btw, is any one of these "sub-processes" associated with algo trading?

For your reference, below is the crash log, taken from Event Viewer.
Could you please help me out with this issue?

Should you need any further information please let me know.

 

Your help is highly appreciated. Thanks in advance!

Regards.

***********************************************************************

Log Name:      Application
Source:        Application Error
Date:          23/11/2022 15:54:29
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:      
Description:
Faulting application name: cTrader.exe, version: 4.4.19.10308, time stamp: 0x636a6098
Faulting module name: ntdll.dll, version: 10.0.22621.755, time stamp: 0x8a328c67
Exception code: 0xc00000fd
Fault offset: 0x000000000003d708
Faulting process ID: 0x0x3A34
Faulting application start time: 0x0x1D8FEA8B01701F6
Faulting application path: C:\Users\user\AppData\Local\Spotware\cTrader\abb70432efbee65d18af69e79fe8efe1\cTrader.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 290209e3-14ea-412a-930e-b6df48ec7302
Faulting package full name:
Faulting package-relative application ID: 

***********************************************************************

Spotware
05 Dec 2022, 08:55

Dear trader,

The team is investigating this issue and will work on a fix. Thanks for reporting this.

Best regards,

cTrader Team

ncel01
05 Dec 2022, 14:11

RE:

Hello Team,

Thanks for the feedback.
For your reference, below are the details of another crash. Now related, apparently, to coreclr.dll

***********************************************************************

Faulting application name: cTrader.exe, version: 4.5.1.10845, time stamp: 0x637e124f
Faulting module name: coreclr.dll, version: 6.0.21.52210, time stamp: 0x61734c6b
Exception code: 0xc00000fd
Fault offset: 0x0000000000049f6e
Faulting process ID: 0x0x49E0
Faulting application start time: 0x0x1D905B5573637E6
Faulting application path: C:\Users\user\AppData\Local\Spotware\cTrader\abb70432efbee65d18af69e79fe8efe1\cTrader.exe
Faulting module path: C:\Users\user\AppData\Local\Spotware\dotnet\shared\Microsoft.NETCore.App\6.0.0\coreclr.dll
Report ID: c9126bc8-ad30-4216-995f-3182d1319ece
Faulting package full name: 
Faulting package-relative application ID: 

***********************************************************************

Spotware said:

Dear trader,

The team is investigating this issue and will work on a fix. Thanks for reporting this.

Best regards,

cTrader Team

ncel01
10 Dec 2022, 19:43

RE: RE:

Hello Team,

Is there any update on these issues?

Thank you.

ncel01 said:

Hello Team,

Thanks for the feedback.
For your reference, below are the details of another crash. Now related, apparently, to coreclr.dll

***********************************************************************

Faulting application name: cTrader.exe, version: 4.5.1.10845, time stamp: 0x637e124f
Faulting module name: coreclr.dll, version: 6.0.21.52210, time stamp: 0x61734c6b
Exception code: 0xc00000fd
Fault offset: 0x0000000000049f6e
Faulting process ID: 0x0x49E0
Faulting application start time: 0x0x1D905B5573637E6
Faulting application path: C:\Users\user\AppData\Local\Spotware\cTrader\abb70432efbee65d18af69e79fe8efe1\cTrader.exe
Faulting module path: C:\Users\user\AppData\Local\Spotware\dotnet\shared\Microsoft.NETCore.App\6.0.0\coreclr.dll
Report ID: c9126bc8-ad30-4216-995f-3182d1319ece
Faulting package full name: 
Faulting package-relative application ID: 

***********************************************************************

Spotware said:

Dear trader,

The team is investigating this issue and will work on a fix. Thanks for reporting this.

Best regards,

cTrader Team

 

Spotware
12 Dec 2022, 10:50

Dear trader,

We were not able to reproduce the root cause of the problem. In order to investigate further, we need the cBot code that reproduces this behavior. If you can share it with us, we will look at this further. 

Best regards,

cTrader Team

ncel01
12 Dec 2022, 21:06 ( Updated at: 21 Dec 2023, 09:23 )

RE:

Hello,

I am affraid that providing the cBot won't be feasible since it contains 5K+ lines of code.

Is the info provided on the event log not enought to already have a clue on what can be the root cause for this?

Moreover, I've got (for several times) an exception, as shown below, mentioning that the problem has been sent to the cTrader team.

Is the development team able to associate such expections with the concerned cTraderID? Could you please verify this?

I believe. that having a clue on the cause would already help for now.

Thank you once again.

Spotware said:

Dear trader,

We were not able to reproduce the root cause of the problem. In order to investigate further, we need the cBot code that reproduces this behavior. If you can share it with us, we will look at this further. 

Best regards,

cTrader Team

Spotware
13 Dec 2022, 12:53

Dear trader,

Unfortunately the log and the exception are not enough to determine the root cause of the issue.

Best regards,

cTrader Team

ncel01
13 Dec 2022, 13:39

RE:

Hello,

The cBot manages dozens of orders OnTick().

Is it possible to, somehow, disable the journal execution? This is using a lot of resources and it can be part of the issue, I believe.

Thank you!

Spotware said:

Dear trader,

Unfortunately the log and the exception are not enough to determine the root cause of the issue.

Best regards,

cTrader Team

firemyst
23 Dec 2022, 01:56 ( Updated at: 21 Dec 2023, 09:23 )

RE:

Spotware said:

Dear trader,

Unfortunately the log and the exception are not enough to determine the root cause of the issue.

Best regards,

cTrader Team

Team @Spotware, this is happening quite a bit! I can't even leave cTrader running cBots overnight with confidence anymore with it crashing after extended periods.

See below. I'm running 2 bot instances on Renko charts:

:

This is probably related to the issue that I reported here:

At least when that was happening, the bots were still able to run! Now everything just crashes.

We can't send any debug information because when cTrader crashes and I click on the "OK" button above, everything disappears. No chance to send any information.

So, if as you say, "Unfortunately the log and the exception are not enough to determine the root cause of the issue." aren't enough info, then @Spotware also needs to update cTrader to capture such information.

This current issue with cTrader crashing on people while running bots seriously needs to be looked into and fixed.

For me to reproduce, I just start a bot on a VPS (2 core, 4GB memory) running at least 2 instances of the same bot. Then I disconnect from the VPS for at least 8 hours and come back to find the error messages.

Spotware
23 Dec 2022, 09:19

Dear firemyst,

The issue you reported does not seem to be related with the problem reported in the initial post. Let us know if you still get the exception in 4.5.3.

Best regards,

cTrader Team

firemyst
23 Dec 2022, 09:59

RE:

Spotware said:

Dear firemyst,

The issue you reported does not seem to be related with the problem reported in the initial post. Let us know if you still get the exception in 4.5.3.

Best regards,

cTrader Team

Hello @Spotware:

The problem reported in the initial post is:

"I've noticed multiple times that, after some hours running cBots, cTrader crashes unexpectedly."

And that's exactly what I've reported in the 9th post in this thread, -- that cTrader is crashing after some hours of running cBots. I even posted a screen capture of it.

So how is it not related? The only difference is I'm running cBots on a VPS with Renko charts versus the OP's running on a personal computer with Windows 11.

firemyst
28 Dec 2022, 10:59 ( Updated at: 21 Dec 2023, 09:23 )

RE:

Spotware said:

Dear firemyst,

The issue you reported does not seem to be related with the problem reported in the initial post. Let us know if you still get the exception in 4.5.3.

Best regards,

cTrader Team

@SPOTWARE!

It's still happening version 4.5.3.11223, and this time while only running a single cBot instance:

Left a bot alone for 5 hours running on Renko charts and bam! I logged back in to my VPS and the error occurs again.

firemyst
29 Dec 2022, 15:29

RE:

Spotware said:

Dear firemyst,

The issue you reported does not seem to be related with the problem reported in the initial post. Let us know if you still get the exception in 4.5.3.

Best regards,

cTrader Team

And yet again...

ncel01
29 Dec 2022, 16:13 ( Updated at: 21 Dec 2023, 09:23 )

RE: RE:

Hi firemyst,

When "automated" trading is not really automated..
Fortunately I am no longer facing any exceptions. At least not yet.. However I can expect that cTrader will crash soon since RAM usage is getting cumulative (increasing all the time). I do not find this very logical since cBot is working in a constant loop and RAM usage should remain stable, which is not the case.

Have you also noticed this?

Spotware should keep in mind the obvious: traders are much more interested on an effective and efficient trading platform over anything described as "visually beautiful".

firemyst said:

Spotware said:

Dear firemyst,

The issue you reported does not seem to be related with the problem reported in the initial post. Let us know if you still get the exception in 4.5.3.

Best regards,

cTrader Team

And yet again...