NT7-beta2 : memory grows

[gbulle]

Hi,

just verified this on 7.0.0.3:

SITUATION
one chart with two overlaied instruments;one indicator on two instruments (the ratio Closes[0][0]/Closes[1][0] of the two instruments);
Bollinger on the ratio and Stochastic on the ratio;

if calculate on bar close == true no meory problem but the ratio does not updates as soon as a new bar is formed


As soon as I put calculate on bar close == false the memory grow up
without stopping and the indicator update in a regular way;
if I change again on the fly to calculate on bar close == true the meory revert back to a normal value

Verified with GAIN DEMO connection and with IB "live" connection


Bye

[NinjaTrader_Bertrand]

Thanks for the post - is this on 7.0.0.3 gbulle? If yes, please post the script you used so I can attempt to reproduce here. Thanks

[gbulle]

Nt 7.0.0.3

[NinjaTrader_Bertrand]

Thanks gbulle, please retry with the attaced ratio.cs file - commented out the two unused dataseries in the properties and did then not see the issue...could you please retest? Thanks

[gbulle]

Thanks but the memory consumption grows up

Just verified better:

If I set "calculate on bar close=false" only for RATIO indicator and set
"calculate on bar close=true" for Bollinger of RATIO and STOCHASTIC of Ratio no memory issue!!

The memory issue appear when I set Bollinger of Ratio and Stochastic of ratio to "calculate on bar close=false";

Now with :

RATIO--> calculate on bar close=false
BOLLINGER(RATIO)-->calculate on bar close=true
STOCHASTIC(RATIO)--> calculate on bar close=true

everythink is OK

So it appear that this issue is related to indicators of indicators and not to the ratio indicator

[NinjaTrader_Bertrand]

Thanks for the additional input gbulle, will look into it shortly.

[NinjaTrader_Bertrand]

gbulle, tested various indicator on indicator combinations and did not see memory usage growing when using those on updating each tick. I did run into a multiseries bug we fixed for the next beta already, so I would suggest to recheck into the same setup once we release 7.0.0.4

Thanks for your effort and input.