MetaTrader 4 Build 529 beta released with new compiler - page 60

New comment
 
stringo:
How can it be reproduced? (We couldn't).

Didn't do anything special.

I run a test, wait for it to finish, compile, clear the log, run it again. At some point it crashes.

 
komposter:

Didn't do anything special.

I run a test, wait for it to finish, compile, clear the log, run it again. At some point it crashes.


Most likely it's because of their notorious code protection, which they never want to turn off, so that everyone decides for himself whether he needs it or not.
 

I´ve just tested build 546 (20. November 2013) and my own EA in MQL4 compiles fine. However, I am getting heaps of errors when running a backtest for it, it uses the internal Bolinger Bands indicator of MT4, nothing more, but the journal is full of:


2013.11.20 22:15:26.624 Not enough memory for indicator Bollinger B ands (EURUSD,M5)
2013.11.20 22:15:26.624 Memory handler: cannot allocate 8754048 bytes of memory
2013.11.20 22:15:26.604 Not enough memory for indicator Bollinger Bands (EURUSD,M5)
2013.11.20 22:15:26.604 Memory handler: cannot allocate 8754048 bytes of memory
2013.11.20 22:15:26.107 Not enough memory for indicator Bollinger Bands (EURUSD,M5)
2013.11.20 22:15:26.107 Memory handler: cannot allocate 8754048 bytes of memory
2013.11.20 22:15:26.105 Not enough memory for indicator Bollinger Bands (EURUSD,M5)
2013.11.20 22:15:26.105 Memory handler: cannot allocate 8754048 bytes of memory
2013.11.20 22:15:25.903 Not enough memory for indicator Bollinger Bands (EURUSD,M5)
2013.11.20 22:15:25.903 Memory handler: cannot allocate 8754048 bytes of memory
2013.11.20 22:15:25.895 Not enough memory for indicator Bollinger Bands (EURUSD,M5)
2013.11.20 22:15:25.895 Memory handler: cannot allocate 8754048 bytes of memory
2013.11.20 22:15:25.811 Not enough memory for indicator Bollinger Bands (EURUSD,M5)
2013.11.20 22:15:25.811 Memory handler: cannot allocate 8754048 bytes of memory
2013.11.20 22:15:25.811 Not enough memory for indicator Bollinger Bands (EURUSD,M5)
2013.11.20 22:15:25.811 Memory handler: cannot allocate 8754048 bytes of memory
2013.11.20 22:15:25.811 Not enough memory for indicator Bollinger Bands (EURUSD,M5)
2013.11.20 22:15:25.811 Memory handler: cannot allocate 8754048 bytes of memory

It prints this all the time while running the backtest (open bar only from 1999 to 2013 on EURUSD). In the current official MT4 build, the backtest takes 6 seconds for the mentioned time range on 5M bar open and creates no errors. I am also wondering why it would not be able to allocate 8 megabyte of memory, the whole terminal process just takes 20 megabytes and I have about 7 gig of RAM free and as MT4 is a 32bit process, it can take up to 2 gig of memory. So allocating those 8mb shouldn´t be a problem and it´s surely a bug since in build 509 everything works fine.

Well sure, it´s a BETA, but this rather seems like an alpha if not even internal MT4 indicators work correctly in a backtest.

What I´ve also noticed, in general everything seems to be MUCH slower than in build 509. For example, running the Period_Converter_Auto script (which creates all timeframes from M1 data), takes about 3 minutes in Build 546, while it takes 20 seconds in build 509.
 
dabugen:

What I´ve also noticed, in general everything seems to be MUCH slower than in build 509. For example, running the Period_Converter_Auto script (which creates all timeframes from M1 data), takes about 3 minutes in Build 546, while it takes 20 seconds in build 509.

Remove from period_converter_auto source lines about FileFlush and script will be executed much faster

         FileWriteInteger(ExtHandle, i_time, LONG_VALUE);
         FileWriteDouble(ExtHandle, d_open, DOUBLE_VALUE);
         FileWriteDouble(ExtHandle, d_low, DOUBLE_VALUE);
         FileWriteDouble(ExtHandle, d_high, DOUBLE_VALUE);
         FileWriteDouble(ExtHandle, d_close, DOUBLE_VALUE);
         FileWriteDouble(ExtHandle, d_volume, DOUBLE_VALUE);
         //FileFlush(ExtHandle);
 
stringo:

Remove from period_converter_auto source lines about FileFlush and script will be executed much faster


Slava, here is a really old topic : why is Flush() so slow in mql5 ?

In old mql4 it is much faster, many times faster.

 

There are new indicators and experts for mt4 on the 5's website (there are free ones too)

1) they are not visible in the marker through the terminal (except for 2 products);

2) On the 5K site when I try to download a product that is not in the marking terminal, I see in the same terminal "MQL4 Marketproduct'C' does not exist" (trimming the name of the product to the 1st letter);

3) For some reason the MA indicator was put in the Experts category.

 
ALXIMIKS:

There are new indicators and experts for mt4 on the 5's website (there are free ones too)

1) they are not visible in the marker through the terminal (except for 2 products);

2) On the 5K site when I try to download a product that is not in the marking terminal, I see in the same terminal "MQL4 Marketproduct 'C' does not exist" (trimming the name of the product to the 1st letter);

3) For some reason the MA indicator was put in the Experts category.


They are test products for internal testing.

1. They must appear in the terminal during 24 hours.

2. Check it.

3. Moving Average is a test Expert Advisor based on an MA indicator. We will correct the description.

 
An attempt to download this product from the Market demo and put it on the chart failed: "2013.11.21 11:53:08.631 Market\macd_line_smart EURUSD,H1: Invalid license"...
 
evillive:
An attempt to download this product from the Market demo and put it on the chart failed: "2013.11.21 11:53:08.631 Market\macd_line_smart EURUSD,H1: Invalid license"...

The demo only works in the tester, and on the chart will only work the version that you buy.
 
How about that, I didn't know.
OmegaTube:

The demo only works in the tester and only the version you buy will work on the chart.

Nah, still doesn't work, tester in visual mode - empty indicator window, unnamed something in indicator list with no parameter settings and again in terminal log the same license error...
1...535455565758596061626364656667...161
New comment
Reason: