![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
So you say if I include without buffer (only 2 for few arrows) some calls of other indicators from one present indicator on the chart, it will accumulate the data from all total calls in memory, unlimited?
I am asking because this week often I spend time and seat in the kitchen on my netbook with 1 gb at all, and just now started to write some indicator tests which I thought will handle them with few mb which I have.
So what is solution without Copy Rates? Possible with calling script from expert, and that script after calculations will release the shanks of memory data not needed any more, or not?
The 'shift' and the 'mode' or 'line index' of an indicator (MACD or iCustom(), ...) is not part of the the set-up. In your case:
the set-up is defined by:
and
can be varied without any problem.
All of your calls will not cause the discussed problem!
But if you vary e.g. fast and slow period:
you will end up with 7*8 = 56 different MACDs running independently on your pc.
Well this is valid for at least indicators called by iCustom(). Maybe it is different with the built in indicator functions - I can't remember - but I doubt that.
I have sent in an article for review about how one can solve this problem but I haven't get any since Nov. 22, 2015.
You can use TerminalInfoInteger(x) with x:
TERMINAL_MEMORY_PHYSICAL
Physical memory in the system, Mb
int
TERMINAL_MEMORY_TOTAL
Memory available to the process of the terminal , Mb
int
TERMINAL_MEMORY_AVAILABLE
Free memory of the terminal process, Mb
int
TERMINAL_MEMORY_USED
Memory used by the terminal , Mb
int
You can use TerminalInfoInteger(x) with x:
TERMINAL_MEMORY_PHYSICAL
Physical memory in the system,Mb
int
TERMINAL_MEMORY_TOTAL
Memory available to the process ofthe terminal , Mb
int
TERMINAL_MEMORY_AVAILABLE
Free memory of the terminal process,Mb
int
TERMINAL_MEMORY_USED
Memory used by the terminal ,Mb
int
Never tried but now. What surprised me, TERMINAL_MEMORY_USED showed more than twice the value of the task manager.
When I created a memory usage logger a while ago, I found the figures sketchy too.
I have no deep Windows inside view but may be the calculations are different? Memory that is a) requested but not used yet, b) swapped onto the hd, c) ...?