Recent hard-lockups, multiple machines.
It may be more likely that you are perhaps using beta builds of MetaTester.
Currently the most recent official build is 4755. What build are you using?
Also, have you checked the tester log files for any messages that might indicate possible reasons for the situation?
Please consider which section is most appropriate — https://www.mql5.com/en/forum/172166/page6#comment_49114893
It may be more likely that you are perhaps using beta builds of MetaTester.
Currently the most recent official build is 4755. What build are you using?
Also, have you checked the tester log files for any messages that might indicate possible reasons for the situation?
Hmm, v4817 - but it auto updates and I see no option to choose between "beta" and "release"? It's been years since I installed it, and it's just kept itself up to date since. I will have a look and see how to revert it, thanks.
As for section, I chose General as I was not specifically talking about Advisors or automated trading (for example, and nothing else seemed to fit), so sorry about that.
Edit: Update
I cannot find any mention of a beta/release version choice anywhere. I got my tester agents from https://cloud.mql5.com/ originally, and there is only one download provided. Can you show me where this choice is located?
Update 2: Decided to try reinstalling from the current download at the above URL. This has installed version 4776, with no mention of "beta" testing of any kind. How do I know this one won't gradually update itself to some beta version?
Update 3: It has now auto-updated to 4817 again, from a fresh install. So I don't know what to do about that - there has not been one sign that this is a "beta" release, and it certainly doesn't say so in the app.
- cloud.mql5.com
Unfortunately, MetaQuotes annoyingly pushes out "beta" builds on normal installations quite aggressively, totally against user's preferences. User's take great pains to get around it.
In my case, I only use "portable mode" setups of MetaTrader (which includes MetaTester), and never ever connect to a MetaQuotes Demo accounts, so that it only updates for official builds pushed out by the broker.
It's from this setup, that I then manage my MetaTester Agents, to prevent any unwanted "beta" updates.
I understand that for general users with lesser computer skills, this may be more difficult to do, but unfortunately MetaQuotes likes to shoot its own feet.
Unfortunately, MetaQuotes annoyingly pushes out "beta" builds on normal installations quite aggressively, totally against user's preferences. User's take great pains to get around it.
In my case, I only use "portable mode" setups of MetaTrader (which includes MetaTester), and never ever connect to a MetaQuotes Demo accounts, so that it only updates for official builds pushed out by the broker.
It's from this setup, that I then manage my MetaTester Agents, to prevent any unwanted "beta" updates.
I understand that for general users with lesser computer skills, this may be more difficult to do, but unfortunately MetaQuotes likes to shoot its own feet.
Unfortunately, MetaQuotes annoyingly pushes out "beta" builds on normal installations quite aggressively, totally against user's preferences. User's take great pains to get around it.
In my case, I only use "portable mode" setups of MetaTrader (which includes MetaTester), and never ever connect to a MetaQuotes Demo accounts, so that it only updates for official builds pushed out by the broker.
It's from this setup, that I then manage my MetaTester Agents, to prevent any unwanted "beta" updates.
I understand that for general users with lesser computer skills, this may be more difficult to do, but unfortunately MetaQuotes likes to shoot its own feet.
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: MetaTester64.exe (14836) consumed 55097950208 bytes, MetaTester64.exe (17276) consumed 54354292736 bytes, and MetaTester64.exe (14060) consumed 54171193344 bytes.
The above is from Windows Event Viewer, retreived after having to hard reset.
So, as there are no other people reporting this so far, I am unsure what to conclude here. I have re-installed MetaTester, of course. The PCs in question are otherwise stable (passes OCCT stress testing etc). The only one that isn't doing this runs on dual Xeon CPUs with 64GB RAM - though its PR of under 200 might be keeping potentially problematic jobs away? The two that crash from memory exhaustion have PR >200, so could certain jobs be steered away from the low PR system, hence a possible "bad job" never reaching it?
Would appreciate insight here - is it normal for such massive memory requirements in more recent MQL5 tasks? Why is MetaTester not limiting, based on system resources?
Just an update to all this. I have determined that the version of MetaTester used doesn't matter - this is a memory space (leak?) issue with certain jobs that get allocated to my workers perhaps a few times a week, though there is sometimes up to a week without issue, which to me strongly supports the case for the problem being task related, and not MetaTester.exe itself - although it shouldn't really allow this to happen at all...
When this occurs, all available RAM is used, and then begins filling the pagefile. Having now allowed the pagefile to grow without limit, the problem job(s) will fill all available disk space too. This is not "normal" by any measure. I cannot believe nobody else is getting this problem - and I remind you that this is happening on 3 different machines (2x W10 and 1xW11).
Just an update to all this. I have determined that the version of MetaTester used doesn't matter - this is a memory space (leak?) issue with certain jobs that get allocated to my workers perhaps a few times a week, though there is sometimes up to a week without issue, which to me strongly supports the case for the problem being task related, and not MetaTester.exe itself - although it shouldn't really allow this to happen at all...
When this occurs, all available RAM is used, and then begins filling the pagefile. Having now allowed the pagefile to grow without limit, the problem job(s) will fill all available disk space too. This is not "normal" by any measure. I cannot believe nobody else is getting this problem - and I remind you that this is happening on 3 different machines (2x W10 and 1xW11).
have you searched the russian forum for an appropriate thread to report this to? These bugs are often seen to sooner over in that section of the forum.
I would try searching for a thread such as "Metatrader 5 version XXXX release". with "release" probably being the main word to search for.
have you searched the russian forum for an appropriate thread to report this to? These bugs are often seen to sooner over in that section of the forum.
I would try searching for a thread such as "Metatrader 5 version XXXX release". with "release" probably being the main word to search for.
- 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 rent out my CPU power to others here, which has been fine for a long time. Over the last week or so, I have had 2 machines locking up, caused by MetaTester64.exe. Today, I managed to prevent a full lockup and get some sort of meaningful error - "buffer overflow", classic method of code injection. Has someone found a way to put out malicious jobs/tasks? Going to have to pause all services in the meantime :/
Anyone else getting this? If it was one machine I might brush it off as some fault on that PC, but this is 2 separate systems. One Win10 22H2, the other is W11 23H2.
Appreciate any suggestions, info etc.