Some tools do not work with new 2265 build of MT5 - how to fix? - page 7

New comment
 

We released a MT5 terminal beta-version with fix for ticksize and StringTrim issues.

Please open demo account on MetaQuotes-Demo server to download update

And provide us with feedback.

 
Aytugan Khafizov:

We released a MT5 terminal beta-version with fix for ticksize and StringTrim issues.

Please open demo account on MetaQuotes-Demo server to download update

And provide us with feedback.

This is nice, despite my problem is not related to this fixes, on new Build 2265, is always good to know that MQ Care about very much about our feedbacks. Thanks Aytugan!
I Hope receive good news about my behavior aswell.
 
Aytugan Khafizov:

We released a MT5 terminal beta-version with fix for ticksize and StringTrim issues.

Please open demo account on MetaQuotes-Demo server to download update

And provide us with feedback.

StringTrimRight() issue not fixed with Build 2267.

2019.12.09 12:50:06.219    MT52265_Crash (EURUSD,H1)    Build 2267
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)    Access violation at 0x00007FF763FFDF30 read to 0xFFFFFFFFFFFFFFFF
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)       crash -->  00007FF763FFDF30 488B0E            mov        rcx, [rsi]
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)                  00007FF763FFDF33 4889CE            mov        rsi, rcx
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)                  00007FF763FFDF36 4883E6FC          and        rsi, 0xfc
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)                  00007FF763FFDF3A F6C102            test       cl, 0x2
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)                  00007FF763FFDF3D 74F1              jz         0x7ff763ffdf30
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)   
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)                  00007FF763FFDF3F 488B4A08          mov        rcx, [rdx+0x8]
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)                  00007FF763FFDF43 F6C102            test       cl, 0x2
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)   
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)    00: 0x00007FF763FFDF30
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)    01: 0x00007FF764677139
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)    02: 0x00007FF7646AE10A
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)    03: 0x00007FF76482D1A3
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)    04: 0x00007FF763FEBA66
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)    05: 0x00007FF764171FED
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)    06: 0x00007FF76417CC80
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)    07: 0x00007FF7649ECA6C
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)    08: 0x00007FFB7A977BD4
2019.12.09 12:50:06.371    MT52265_Crash (EURUSD,H1)    09: 0x00007FFB7BFCCED1

 
Alain Verleyen:

StringTrimRight() issue not fixed with Build 2267.

Have you recompiled your EA with new build?

 
Aytugan Khafizov:

Have you recompiled your EA with new build?

Of course.
 
We will perform further checks tomorrow, please wait.
 
Aytugan Khafizov:
We will perform further checks tomorrow, please wait.
Sure, thanks.
 

Hi I did some tests with the 2265 build and see the speed difference on Launching my EA, the time to get the OnInit Event() is much more higher.

Now I used the test on a another Third PC Core i7, the 2265 is much more slower and take a big time to get OnInit(), The 2190 is imediate. For a i5 or i3 it takes much more time than you will see and the difference is much more bigger.

Here Build 2190 Versus 2265 (Detail The RaZop Logo appears on begining of OnInit()).


 
Our developers are working on slowdown issue, please wait for new beta.
 

Hello everyone,

Since the new update, in backtest ...

my EA tries to open \ close positions (which implies that I get a tick) and

I say '' try '' because it does not happen because it considers that the [market is closed].

Before the update everything went well.

Would you have seen this same problem?

If yes how to fix it, would you have an idea?

Thank you.
123456789101112
New comment