NT8 B11: Platform crashes with the same error

[sledge]

I did find another post with the same error... but doesn't look related all that much.

http://ninjatrader.com/support/forum/showthread.php?t=85995&highlight=ninjascriptbase+get_bars

[karlomacariola]

Thanks for the link. I've seen that as well and it's pretty much the only post that I can find that had the same issue. I don't know whatever happened to that though.

[sledge]

I'm trying to reproduce this in Playback-MR on ES 09-16.

I added some random DataSeries types.

Is there anything I should focus in more on?

I will try a 1 Tick series since that what the other post had next run.

Different Panels or single like I've done or Overlay?

Or are you using this in a strategy?

http://screencast.com/t/jpqvSeiq0xk

		protected override void OnStateChange()
		{
			if (State == State.SetDefaults)
			{
				Description									= @"Enter the description for your new custom Indicator here.";
				Name										= "MyCustomIndicator";
				Calculate									= Calculate.OnEachTick;
				IsOverlay									= false;
				DisplayInDataBox							= true;
				DrawOnPricePanel							= true;
				DrawHorizontalGridLines						= true;
				DrawVerticalGridLines						= true;
				PaintPriceMarkers							= true;
				ScaleJustification							= NinjaTrader.Gui.Chart.ScaleJustification.Right;
				//Disable this property if your indicator requires custom values that cumulate with each new market data event. 
				//See Help Guide for additional information.
				IsSuspendedWhileInactive					= true;
				AddPlot(Brushes.Orange, "Plot1");
				AddPlot(Brushes.Brown, "Plot2");
				AddPlot(Brushes.IndianRed, "Plot3");
				AddPlot(Brushes.LightSalmon, "Plot4");
				AddPlot(Brushes.Chocolate, "Plot5");
				AddPlot(Brushes.Orange, "Plot6");
				AddPlot(Brushes.DarkRed, "Plot7");
			}
			else if (State == State.Configure)
			{
				AddDataSeries ( "ES 09-16", BarsPeriodType.Minute, 1);
				AddDataSeries ( "ES 09-16", BarsPeriodType.Minute, 3);
				AddDataSeries ( "ES 09-16", BarsPeriodType.Minute, 5);
				AddDataSeries ( "ES 09-16", BarsPeriodType.Second, 45);
				AddDataSeries ( "ES 09-16", BarsPeriodType.Range , 4);
				AddDataSeries ( "ES 09-16", BarsPeriodType.Range , 6);
				AddDataSeries ( "ES 09-16", BarsPeriodType.Tick, 100);
				//AddDataSeries ( "ES 09-16", BarsPeriodType.Volume, 1000);
				
			}
		}

[karlomacariola]

Hi sledge. Thanks for your help. I've been running this test indicator on a live Kinetick feed (I haven't tried it on Playback connection). Also, I cannot tell when the error occurs - sometimes it takes less than an hour or several hours before the platform crashes but when it happens the last lines in the trace files are the same. I am currently running the indicator (with the Print lines) as I am writing this, waiting for it to break.

[karlomacariola]

Oh BTW it's an indicator with DrawOnPricePanel set to false so it has its own indicator panel.

[sledge]

I've played around with this some tonight - and found some issues in Playback-MR...

Mostly - if you changed tabs while in replay - with my code posted below - on the last plot is on the chart...

And I can not get this thing to plot in ES 03-16 tab... it shows up on the right side scale.. but not plots.

I may have to recreate my chart and save my workspace again...

But still - no crashes as of yet in playback-MR... (which is not Kinetick Live...) .. I'm trying with what I got here..

[karlomacariola]

Hi sledge. I did what you told and added the Print lines to check if we can get more clues as to what causes this error.

protected override void OnBarUpdate()
		{
			//Add your custom indicator logic here.	
			
			for (int i = 0; i < 8; i++)
			{
				if (CurrentBars[i] < 1)
					return;
			}
			
			if(BarsInProgress == 1) {
				if(Opens[1].IsValidDataPoint(0)) {
					double rsi = RSI(Opens[1], 14, 1)[0];
					Print("RSI(Opens[1], 14, 1)[0] = " + rsi);
					Plot1[0] = rsi;
				}
			}
			if(BarsInProgress == 2) {
				if(Closes[2].IsValidDataPoint(0)) {
					double rsi = RSI(Closes[2], 14, 1)[0];
					Print("RSI(Closes[2], 14, 1)[0] = " + rsi);
					Plot2[0] = rsi;
				}
			}
			if(BarsInProgress == 3) {
				if(Highs[3].IsValidDataPoint(0)) {
					double rsi = RSI(Highs[3], 14, 1)[0];
					Print("RSI(Highs[3], 14, 1)[0] = " + rsi);
					Plot3[0] = rsi;
				}
			}
			if(BarsInProgress == 4) {
				if(Lows[4].IsValidDataPoint(0)) {
					double rsi = RSI(Lows[4], 14, 1)[0];
					Print("RSI(Lows[4], 14, 1)[0] = " + rsi);
					Plot4[0] = rsi;
				}
			}
			if(BarsInProgress == 5) {
				if(Opens[5].IsValidDataPoint(0)) {
					double rsi = RSI(Opens[5], 14, 1)[0];
					Print("RSI(Opens[5], 14, 1)[0] = " + rsi);
					Plot5[0] = rsi;
				}
			}
			if(BarsInProgress == 6) {
				if(Closes[6].IsValidDataPoint(0)) {
					double rsi = RSI(Closes[6], 14, 1)[0];
					Print("RSI(Closes[6], 14, 1)[0] = " + rsi);
					Plot6[0] = rsi;
				}
			}
			if(BarsInProgress == 7) {
				if(Highs[7].IsValidDataPoint(0)) {
					double rsi = RSI(Highs[7], 14, 1)[0];
					Print("RSI(Highs[7], 14, 1)[0] = " + rsi);
					Plot7[0] = rsi;
				}
			}
		}

But after running the indicator for about 3 hours it crashed and the only error message that I could find is still the same one from the trace file. The Output window shows no error.



It just happens randomly.

[karlomacariola]

Are we just going to ignore this?

[sledge]

Are we just going to ignore this?

Sometimes it takes a few days for them to "Catch Up"...

In my experience - more recent issues are addressed first, then they catch up to the "earlier" issues....

This is definitely not a FIFO queue.

I'm even waiting for a response .. http://ninjatrader.com/support/forum...ad.php?t=87898

[NinjaTrader_ChelseaB]

Hi karlomacariola,

Note that NinjaTrader 8 beta items fall secondary in priority to NinjaTrader 7 inquiries.
Per the NinjaTrader 8 beta help guide: Bug reports will be reviewed by our support and development staff inside of a 48 hour period.
See the link below on Bug reports and providing feedback.

http://ninjatrader.com/support/helpGuides/nt8/en-us/?beta.htm

Regarding the script. After seeing your post 19 letting us know the error occurs randomly I allowed the script to run continuously on another testing computer. I started the test at 10:23 Eastern yesterday and the error was reproduced at 5:44 AM Eastern this morning.

I am currently further investigating so that I can make a report.

[NinjaTrader_ChelseaB]

Hi karlomacariola,

Thanks for your patience.

This error went in to our bug tracking system and was marked as already corrected for Beta 13 from a fix done for another similar error tracked with ID #NTEIGHT-10139.

(I have verified over 2 days of continuous use that the error is corrected with the latest build)

Please wait until Beta 13 is released and test for this behavior once more.

[karlomacariola]

Hi Chelsea. Many many thanks for looking into this. We look forward to the release of the latest build and we appreciate your efforts in resolving this bug.

Karlo

[karlomacariola]

Update

Hi Chelsea. I wanted to follow up on the same issue described in the beginning of the thread. I have updated my NinjaTrader 8 client to version 13 RC1 and have proceeded to test our indicators which I was very much looking forward to since we were told that the issue we raised here was going to be addressed in the next iteration. Unfortunately while testing for several minutes the platform crashed as before and when I checked the end of the last trace file I saw the same error:

2016-09-06 22:42:43:723 Gui.Chart.ChartPanel.OnRender: System.IndexOutOfRangeException: Index was outside the bounds of the array.
at NinjaTrader.NinjaScript.NinjaScriptBase.get_Bars()
at NinjaTrader.Gui.NinjaScript.IndicatorRenderBase.Ca lculateMinMax()
at NinjaTrader.Gui.Chart.ChartScale.CalculateMinMax()
at NinjaTrader.Gui.Chart.ChartPanel.CalculateMinMax()
at NinjaTrader.Gui.Chart.Direct2DForm.RenderInit()

The same error is observed when running the sample code I added here in the thread after running it for several minutes. I understand that you have speculated that this is somewhat connected to a "similar" bug with the tracking code ID #NTEIGHT-10139 and it does seem to have been fixed in the latest version according to its release notes; however apparently it is a different bug all on its own. We would be grateful if you can advise us further with the status of this issue. Many thanks once again for your attention on this and all best wishes.

Karlo

[NinjaTrader_PatrickH]

Hello karlomacariola,

Thank you for your update.

We will continue to investigate on our end. I will follow up with you here when I have any additional information.

[karlomacariola]

Hi Patrick. Many thanks for looking into this and we look forward to your updates.

Karlo