I mean that the absence of possibility to unload an indicator from the memory in the tester will lead to suspension of the system, if, for example, you optimize indicators by your own means on the fly. Or, for example, changing indicator parameters dynamically will lead to memory overflow, because every time a new handle will be created and the old one won't be deleted in the tester.
A necessary and relevant one at the moment. I was looking for the cause myself for a long time, thought it was a bug in my code, thanks to this thread the problem has been solved.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
The number of windows is clear, but the number of MA with different parameters how to determine?
It is very important to make an IndicatorRelease of its handle BEFORE OnDeinit.
Interestingly, after each such IndicatorRelease, the indicator handle is incremented by one.
Figured it out
It is very important to make an IndicatorRelease of its handle BEFORE OnDeinit.
Interestingly, after each such IndicatorRelease, the indicator handle is incremented by one.
Is IndicatorRelease working in the tester yet? Just in case - it didn't work before.
I haven't tested it.
Good topic
A necessary and relevant one at the moment. I was looking for the cause myself for a long time, thought it was a bug in my code, thanks to this thread the problem has been solved.
Thank you all!