Thank you for report. Memory leak fixed.
stringo:
Thanks very much for looking into this, looking forward to the next update.
Thank you for report. Memory leak fixed.
Is there a memory leak in the newest version? I have some of the .exe processes getting up into the 4gb+ range or higher. I also had one pc almost freeze entirely because metatester took all available ram.
DarkRyder:
Is there a memory leak in the newest version? I have some of the .exe processes getting up into the 4gb+ range or higher. I also had one pc almost freeze entirely because metatester took all available ram.
Why are you posting in an old thread ? Please use the good topic (or this one).
Is there a memory leak in the newest version? I have some of the .exe processes getting up into the 4gb+ range or higher. I also had one pc almost freeze entirely because metatester took all available ram.
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
Ok, I have been playing around with a class I had written for weeks now, trying to get to the bottom of a strange problem. For debugging purposes it seems logical to do the debugging of the workings of a class in a script, and whence the class is functional, import it into your expert. When doing this I noticed some descrepencies between the results (which have for all but one been solved), but the most notable was the fact that metatester.exe seemed to be increasing in ram usage linearly with time. It is important to state here that the script equivalent ran flawlessly and showed no such problems.
After retesting my own code numerous times I finally came to the conclusion it must have been something to do with the API calls to the indicator or the array buffers (my program uses an iterative creation and destruction of indicators for analysis). To test this I have created a simpler class which basically outlines where I thought the fault might have originated from. Interestingly enough, the same problem seems to arise, except 100x worse (I'm assuming partly because the intermediary calculations have been taken out). Running this code in an expert crashes my computer in a very short amount of time, however in a script seems to do exactly what it is supposed to. Please note this class is in no way of any use, its simply to test if the calls are working as intended.
If however I have made some totally illegal use of the array manipulation calls or indicator calls, my apologies. This particular problem however appears to me more reminiscent of a bug in the metatester.exe process.
I have attached the code below, and for the sake of completion my tester log file. Please use with caution as this has crashed my machine.