script memory leak?

New comment
 
Both of the methods below seem to execute fine, but when the scripts are removed or replaced a massive number of print messages appear on the screen with historic data. Is this confirmed by other people in Build 204? Is there a work around? I'm actually building a polling script, and the print statement is just a demo.

int start()
{
RefreshRates();
Print("New quote, ", Ask, " ", Bid);
Sleep(15000);
start();
return(0);
}

int start()
{
while(true)
{
RefreshRates();
Print("New quote, ", Ask, " ", Bid);
Sleep(15000);
}
return(0);
}
 
No memory leak's. We have used lazy print method.
 
Why does it generate print messages when it is asleep?
 
I'm having a similar problem with the same code when running an EA. The issue is much smaller but still occurs. When running a script, I was very concerned the machine would simply die after running the script in a loop for a few hours since several minutes completely locked up the trading terminal.

With an EA, here are a few results with screenshots. The EA ran for 3 minutes with 12 ticks recorded (Exactly correct for a 15 second delay). Upon removing the EA, 26 more messages filled the screen (compared to uncountable thousands for the script).

Maybe you're doing garbage collection and there is no memory leak? Is the message queue flushed on a regular basis? Why is sleep() broken?

My entire goal is to enter trades on a timer, rather than on a tick. The timer is a heartbeat system for examining a change in a DLL variable. If there is another way of doing this that is not tick dependent, please let me know.



And the flood of messages on removing the expert:
 
I watched it eat memory for nearly 2 hours, then it flushed the queue and dropped memory usage again. The reason I'm so concerned over the extra print statements is because those might be extra trades in the future :/ A work around in the worst case scenario would be to close the EA every Friday night.
New comment