DislikedSometimes I let run the terminal for days or weeks. Its not the Problem. The Problem was, MT4 cant handle so many single MTF Dashboards {quote}Ignored
The problem is, every buffer of every indicator stores a 'double' value for every bar.
A double value is not particularly big (8 bytes).
But let's do the maths: let's say a hypothetical dashboard makes 6 iCustom calls for each of the 28 pairs it tracks. Each iCustom indicator has 3 buffers.
(NB I don't know how many iCustom calls your dashboard makes, but you can get an idea by looking in the Journal when you first apply it)
6 indicators x 28 pairs x 3 buffers =504 double values stored per bar.
Now let's say there is the default 65,000 bars on the chart.
65,000 x 504 = 32,760,000 double values.
We already said that a double is 8 bytes.
The memory load for this hypothetical dashboard is (32,760,000 * 8 = 262,080,000 bytes) 262 MB
Now let's make that 3 dashboards = 786 MB on our hypothetical dashboard
Pretty steep, but not too much. OK, but what happens when a new bar arrives? Unfortunately MT4 doesn't release the memory of the old bars until you restart the terminal. So when you get to 65,001 bars, it doesn't drop the oldest. It keeps going. On an M1 chart, you are adding 1,440 bars per day, per chart.
You see the problem if you don't restart your terminal?
Sure, there may well be CPU issues too depending on how the dashboard is written. But don't discount the memory issue.
Try adding the memory usage indicator to a terminal that has been running for a few weeks and note the usage. Then restart the terminal and compare the usage of the freshly opened terminal. You may be surprised.