Memory exception
Looks like there was some memory usage peak in your PC (for a few seconds/milliseconds) that could be caused by literally anything. When the terminal tried to allocate some more memory, the system couldn't give it any, so it threw this exception and handled it by printing this message. Also looks like the memory allocation was not critical to the program, so it continued its execution flow normally - at least, all of this is what I deduced, and if that is the case, this issue would be quite hard to prevent.
If you had an EA running at the time (even if it was a simple trading panel), I would suggest you to review the code and take a look if there is some place where you allocate memory using the new keyword. If so, check if you properly release that object using delete whenever it is not needed anymore.
If the error persists, it would be better to contact the support team.
If the error persists, it would be better to contact the support team.
How do I do that?
note that I hadnt done a reboot since that issue I described, therefore my new issues probably are just an extension or continuation of same issue. But I have real issues now. Not just those 2 lines described above...
NE 2 14:48:21.651 MQL5 VirtualAlloc failed in large allocator, size=1262176
ER 2 14:48:21.652 MQL5 VirtualAlloc failed in large allocator, size=1262176
MK 2 14:48:21.652 MQL5 VirtualAlloc failed in large allocator, size=210376
GQ 2 14:48:21.652 MQL5 VirtualAlloc failed in large allocator, size=1262176
HO 2 14:48:21.908 MQL5 VirtualAlloc failed in large allocator, size=1262128
FE 2 14:48:21.908 MQL5 VirtualAlloc failed in large allocator, size=1262128
KR 2 14:48:21.909 MQL5 VirtualAlloc failed in large allocator, size=1262128
GH 2 14:48:22.034 MQL5 VirtualAlloc failed in large allocator, size=1262368
QQ 2 14:48:22.034 MQL5 VirtualAlloc failed in large allocator, size=1262368
KO 2 14:48:22.034 MQL5 VirtualAlloc failed in large allocator, size=1262368
EE 2 14:48:22.034 MQL5 VirtualAlloc failed in large allocator, size=1262368
OR 2 14:48:22.034 MQL5 VirtualAlloc failed in large allocator, size=1262368
IH 2 14:48:22.034 MQL5 VirtualAlloc failed in large allocator, size=1262368
GF 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1262128
DO 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1261456
CE 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1262128
GR 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1261600
FH 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1261456
KF 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1261600
IL 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=210256
HF 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=210280
JR 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1261456
OH 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1261600
GF 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1262128
DO 2 14:48:22.835 MQL5 VirtualAlloc failed in large allocator, size=1261792
RE 2 14:48:22.835 MQL5 VirtualAlloc failed in large allocator, size=1261792
QQ 2 14:48:22.835 MQL5 VirtualAlloc failed in large allocator, size=210312
PH 2 14:48:22.835 MQL5 VirtualAlloc failed in large allocator, size=1261792
NF 2 14:48:23.414 MQL5 VirtualAlloc failed in large allocator, size=1262320
DO 2 14:48:23.414 MQL5 VirtualAlloc failed in large allocator, size=1262320
RE 2 14:48:23.414 MQL5 VirtualAlloc failed in large allocator, size=1262320
RR 2 14:48:23.414 MQL5 VirtualAlloc failed in large allocator, size=1262128
LH 2 14:48:23.414 MQL5 VirtualAlloc failed in large allocator, size=1262128
FF 2 14:48:23.414 MQL5 VirtualAlloc failed in large allocator, size=1262128
EO 2 14:48:24.042 MQL5 VirtualAlloc failed in large allocator, size=1262224
KE 2 14:48:24.042 MQL5 VirtualAlloc failed in large allocator, size=1262224
DP 2 14:48:24.042 MQL5 VirtualAlloc failed in large allocator, size=210384
IH 2 14:48:24.042 MQL5 VirtualAlloc failed in large allocator, size=1262224
IF 2 14:48:32.734 MQL5 VirtualAlloc failed in large allocator, size=1261936
KO 2 14:48:32.734 MQL5 VirtualAlloc failed in large allocator, size=1261936
EE 2 14:48:32.734 MQL5 VirtualAlloc failed in large allocator, size=1261936
I started a Complete Optimisation, but on a 2nd mt5 terminal. not the same terminal as the issue earlier, however, I had not done a system reboot. SO I guess this is almost certainly a continuation of the same issue. The system then locked up, and I was forced to do a forced system reboot. I did corruption check of drives with 0 errors. The eas appear to be working 100%. See full log file attached.
Never used it, but trying the Contacts and requests link down below the page should help you contact the service desk somehow.
The log didn't help that much. It shows you had enough memory when the terminal was launched, but not at the time the errors occured. Since VirtualAlloc is a Windows function, I would still bet this is a system issue not related to metatrader, but we don't know how MQL5 programs allocate memory under the hood - they may use VirtualAlloc or may not. However, if you have the code for your EAs/indicators, I would still recommend you to check if there is some memory allocation and, if so, if you deallocate it correctly - it's not uncommon to have memory issues due to some error in a MQL5 program.
Also, if you cannot contact the service desk, if your code is correct and if the problem persists after rebooting, the only option I can see here to identify the issue is to activate each EA/indicator at a time to detect if one of them specifically is the cause of the problem. If possible, try running your EAs on a different computer (like a AWS/Azure/Google Cloud VM). In the case the issue disappears, there should be something related to your machine that is causing the error, which would be really hard to fix without further details.
use of new and delete are beyond my current mql5 coding skills. I have only used if,else and a single loop -- and called a couple indicators as resources; the indicators are nested code also; which is about the limits of my mql5 coding skills. I am sure that I could learn more if i had the time, however I do not.
But all seems to work, no errors in weeks before this, of the eas running well. Each ea is less than 900 lines, devided into at least 10 functions -- yes I intend to break it up a bit more. This is only 2 eas, 1 ea manages ALL trades and open trades on the same chart, while a 2nd ea is on all the other 15 charts that only open trades.
i have just now finished running a debug on both eas, and on both terminals without any exclamation lines or red errors. There are 0 messages or errors in experts and journal tabs that are abnormal.
Is there anything you would suggest that I do to analyse mt5 or the system before I declare the issue was a "one off"???
and just fyi the Contacts and requests shows this
Technical issues
If you have any technical questions related to the platform, website, services or MQL5 language features, ask them on the Forum. You can also share your suggestions for developing our projects there.
and then it has a button that says Ask on the Form, which forwards one to the forum. no special group, just the same page that you go to when you clike the forum link at the top of the page.
How do I do that?
note that I hadnt done a reboot since that issue I described, therefore my new issues probably are just an extension or continuation of same issue. But I have real issues now. Not just those 2 lines described above...
NE 2 14:48:21.651 MQL5 VirtualAlloc failed in large allocator, size=1262176
ER 2 14:48:21.652 MQL5 VirtualAlloc failed in large allocator, size=1262176
MK 2 14:48:21.652 MQL5 VirtualAlloc failed in large allocator, size=210376
GQ 2 14:48:21.652 MQL5 VirtualAlloc failed in large allocator, size=1262176
HO 2 14:48:21.908 MQL5 VirtualAlloc failed in large allocator, size=1262128
FE 2 14:48:21.908 MQL5 VirtualAlloc failed in large allocator, size=1262128
KR 2 14:48:21.909 MQL5 VirtualAlloc failed in large allocator, size=1262128
GH 2 14:48:22.034 MQL5 VirtualAlloc failed in large allocator, size=1262368
QQ 2 14:48:22.034 MQL5 VirtualAlloc failed in large allocator, size=1262368
KO 2 14:48:22.034 MQL5 VirtualAlloc failed in large allocator, size=1262368
EE 2 14:48:22.034 MQL5 VirtualAlloc failed in large allocator, size=1262368
OR 2 14:48:22.034 MQL5 VirtualAlloc failed in large allocator, size=1262368
IH 2 14:48:22.034 MQL5 VirtualAlloc failed in large allocator, size=1262368
GF 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1262128
DO 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1261456
CE 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1262128
GR 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1261600
FH 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1261456
KF 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1261600
IL 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=210256
HF 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=210280
JR 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1261456
OH 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1261600
GF 2 14:48:22.234 MQL5 VirtualAlloc failed in large allocator, size=1262128
DO 2 14:48:22.835 MQL5 VirtualAlloc failed in large allocator, size=1261792
RE 2 14:48:22.835 MQL5 VirtualAlloc failed in large allocator, size=1261792
QQ 2 14:48:22.835 MQL5 VirtualAlloc failed in large allocator, size=210312
PH 2 14:48:22.835 MQL5 VirtualAlloc failed in large allocator, size=1261792
NF 2 14:48:23.414 MQL5 VirtualAlloc failed in large allocator, size=1262320
DO 2 14:48:23.414 MQL5 VirtualAlloc failed in large allocator, size=1262320
RE 2 14:48:23.414 MQL5 VirtualAlloc failed in large allocator, size=1262320
RR 2 14:48:23.414 MQL5 VirtualAlloc failed in large allocator, size=1262128
LH 2 14:48:23.414 MQL5 VirtualAlloc failed in large allocator, size=1262128
FF 2 14:48:23.414 MQL5 VirtualAlloc failed in large allocator, size=1262128
EO 2 14:48:24.042 MQL5 VirtualAlloc failed in large allocator, size=1262224
KE 2 14:48:24.042 MQL5 VirtualAlloc failed in large allocator, size=1262224
DP 2 14:48:24.042 MQL5 VirtualAlloc failed in large allocator, size=210384
IH 2 14:48:24.042 MQL5 VirtualAlloc failed in large allocator, size=1262224
IF 2 14:48:32.734 MQL5 VirtualAlloc failed in large allocator, size=1261936
KO 2 14:48:32.734 MQL5 VirtualAlloc failed in large allocator, size=1261936
EE 2 14:48:32.734 MQL5 VirtualAlloc failed in large allocator, size=1261936
I started a Complete Optimisation, but on a 2nd mt5 terminal. not the same terminal as the issue earlier, however, I had not done a system reboot. SO I guess this is almost certainly a continuation of the same issue. The system then locked up, and I was forced to do a forced system reboot. I did corruption check of drives with 0 errors. The eas appear to be working 100%. See full log file attached.
This error is very difficult to figure out.
That's years I am seeing it from time to time, and was not yet able to catch it.
EE 2 14:48:32.734 MQL5 VirtualAlloc failed in large allocator, size=1261936
I started a Complete Optimisation, but on a 2nd mt5 terminal. not the same terminal as the issue earlier, however, I had not done a system reboot. SO I guess this is almost certainly a continuation of the same issue. The system then locked up, and I was forced to do a forced system reboot. I did corruption check of drives with 0 errors. The eas appear to be working 100%. See full log file attached.
It looks to me like your system ran out of memory, both physical (RAM) and virtual (page).
It looks to me like your system ran out of memory, both physical (RAM) and virtual (page).
thats how it looked yes. However I checked Task Manager -- as if it does not lie (haha) -- and i had 15gb of 64gb free, and had for at least 3 minutes, which would have been during the time of that half page of errors.
But as I also said, those errors occured on same system boot as the original post of the 2 lines
"2024.06.05 05:45:36.854 MemoryException 7471104 bytes not available, 0 heapmin result"
there was at least 2 hours between each event, however, I think that both events would be related to each other since they both happened on the same windows boot up. I did not have any other errors or symtoms after the initial messages, so I did not do a reboot until the system locked up -- after the 2nd event occured a couple hours after those initial dual messages.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
message in Jounal (2 lines with same message, 1 below the 2nd) "2024.06.05 05:45:36.854 MemoryException 7471104 bytes not available, 0 heapmin result"
Several Trade messages within half hour after that went without a hitch and other trades opened and closed since that event, so mt5 seems to have continued despite the memory exception.
Should I be concerned with it? is there a log that will give me more details that I can report or post?
I have a mini pc, with intel cpu 12450 and 64gb memory with at least 25gb free at the time of the exception. I know for sure that the system was awake at the time of the event and I was watching a movie in full screen mode in movie program Media Player Classic.
I only noticed the exception message after couple hours after it happend. so, no glitches or flickers that might have given me alert of any system failure of any sort.