5 Jun 2013, 10:30
Sorry. Yes, of course. How silly of me not to have given you a copy of the project with the fault.
Here it is...
......
so.mq5
Stack Overflow in tester after n edits in fxDreema
-
I know I posted about this before, but I've experienced the problem again today.
After a certain (high-ish) number of edits, re-edits and compilations my tester stops with "Stack Overflow". When I've calmed down again, I then laboriously re-type the whole EA into a new file in fxDreema, and the problem goes away.
Therefore it kinda looks like a corruption during an edit/re-edit after a number of times.
-
So this error comes after you edit something in the output code? What is it that you change?
-
I think it occurred after I'd amended the text in a block's title or simply moved a block on the screen. I think it was that simple! I don't know what I was doing when the first one happened.
-
The output code is generated depending on the block parameters, not their title or position. How many blocks do you have?
-
I have 15 blocks and 8 variables. In retrospect I think what I did just before the Stack Overflow error was to change the value of a numeric variable. I think I also amended a block title and may have moved the block on screen too; but the main thing was changing the value in the variable.
-
Well, I don't have a crystal ball and unfortunately I don't know many details about this error. Stack overflow is something related to memory size, but what exactly... If you have a project where this error exists and this project is not secret, give it to me so I can inspect it.
-
Sorry. Yes, of course. How silly of me not to have given you a copy of the project with the fault.
Here it is...
......
so.mq5 -
Disconnect block 6 from itself
-
Ah... we may be getting to the heart of the matter now. As you see from my screen shot, block 6 is, as far as its concerned, disconnected from itself. Could this be where the corruption is creeping in? FxDreema seems to think one thing, and the underlying code another?
......
Clipboard0223.jpg -
Could this be a connected issue? I seem to get this error upon exiting from fxDreema from time to time, maybe after a file has become corrupted. This particular occurrence of this error happened when I exited fxDreema just now after editing the so.mq5 file with the corruption.
......
Clipboard0111.jpg -
__Ah... we may be getting to the heart of the matter now. As you see from my screen shot, block 6 is, as far as its concerned, disconnected from itself. Could this be where the corruption is creeping in? FxDreema seems to think one thing, and the underlying code another?[/quote:cx0h0z99]
It is self-connected, notice the tiny black things around it's input and output circles. Right-click on it, hit "Detach", then connect it again with the other two blocks.The local version of fxDreema is builted with 3rd party software and I am total noob in the world of desktop programming (C/C++), so I can't help much with the other error.
-
...oh ...and then this message appears after a good bit of disk activity...
......
Clipboard01112.jpg -
Ah!
Tiny black things! Yes. Never spotted them before! Now the EA is working. I have no idea how this block became self-connected. I didn't do it deliberately! Maybe it would be possible to code fxDreema to check for this sort of thing and do an "are you sure?"Anyway, I'll now look out for this first if Stack Overflow appears.
Thank you!
-
This can be used sometimes to create infinite loop... but when - I don't know
Connecting the negative output to the input has more logic. Before those little black things were bigger before, but I decided to make connections with less curviness... and now I see that their wicks are invisible in. Maybe I will try to make those self-connections to appear above the block, not behind it.Are you trying to install the new build? Because in it, the first thing to do is to backup all the data and then to update some files because of some new rules that I've made. If you have many projects, and they have many small files, this backup process can take some seconds, maybe minute, but if you decide to close the program in the middle of the process it will hang of course.
When is that disk activity starting? Hitting .ex4 or something else?
-
The disk activity starts after hitting the OK on the "Runtime Error!" message.
I'm working on build 037 (01 May 2013). Is there a newer one? The local version isn't telling me there is.
I've also just realised that the really useful Filter Trade Event blocks don't seem to be available in MQL5. Do you plan to add them?
......
Clipboard01113.jpg -
Oops, I found a problem with reading the last available build, and unfortunately the problem is in the .exe, not on the server. I will create a new build now (039).
It was interesting to me when someone will ask for these blocks
MT5 actually natively supports this event. I have plan to make them.
