I'm running a backtest on one of my EAs on mt4 build 625 and suddenly the backtester will stop, like it is paused but I didn't pause it (also I'm not running visual mode). It seems to always do this whenever 7 trades are opened simultaneously.
Then I ran it in visual mode at the dates where the freezing took place and noticed the same thing. Whenever there was more than 7 trades. It seemed to happen in the GBPJPY pair. but other pairs I tested it appears to be fine.
Sometimes I cannot get the terminal to 'stop' the tester when I click the stop button. It seems that if the version of the EA used was compiled in metaeditor mt4 509, then the freezing results in a forced kill to kill the entire terminal. If the similar EA compiled in mt4 build 625, then the stop button takes about 5-10 seconds to stop the testerbut I do not have to kill the terminal.
No errors in the terminal journal while the backtest is functioning. AFTER the stop button is pushed and if the stop is successful, the terminal will read:
I will do a reboot of the computer and see if that changes anything, but it seems like a bug.

- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
I'm running a backtest on one of my EAs on mt4 build 625 and suddenly the backtester will stop, like it is paused but I didn't pause it (also I'm not running visual mode). It seems to always do this whenever 7 trades are opened simultaneously.
Then I ran it in visual mode at the dates where the freezing took place and noticed the same thing. Whenever there was more than 7 trades. It seemed to happen in the GBPJPY pair. but other pairs I tested it appears to be fine.
Sometimes I cannot get the terminal to 'stop' the tester when I click the stop button. It seems that if the version of the EA used was compiled in metaeditor mt4 509, then the freezing results in a forced kill to kill the entire terminal. If the similar EA compiled in mt4 build 625, then the stop button takes about 5-10 seconds to stop the testerbut I do not have to kill the terminal.
No errors in the terminal journal while the backtest is functioning. AFTER the stop button is pushed and if the stop is successful, the terminal will read:
I will do a reboot of the computer and see if that changes anything, but it seems like a bug.