Ninja seems to crash if you press F5 while reloading data

[gomifromparis]

Hi,

Scenario 1
1. I open a 15 tick DAX chart
2. I click "reload historical data"
3. While data reloading, I keep typing F5, about 2 times per second.

=> result OK

Scenario 2
1. I open a 15 tick DAX chart
2. I add any indicator (example SMA)
3. I click "reload historical data"
4. While data reloading, I keep typing F5, about 2 times per second.

=> result Ninja crash

trace :
2012-04-05 14:24:01:339 in OnUnhandledApplicationException
2012-04-05 14:24:01:342 *************** unhandled exception trapped ***************
2012-04-05 14:24:01:343 L'index se trouve en dehors des limites du tableau.
2012-04-05 14:24:01:343 System.IndexOutOfRangeException: L'index se trouve en dehors des limites du tableau.
à NinjaTrader.Gui.Chart.ChartControl.ApplyIndicators Strategies()
à NinjaTrader.Gui.Chart.ChartControl.OnMenuItem(Obje ct sender, EventArgs e)
à NinjaTrader.Gui.Chart.ChartControl.HotKey(Keys keys)
à NinjaTrader.Gui.Chart.ChartForm.HotKey(Keys keys)
à NinjaTrader.Data.HotKeyMessageFilter.PreFilterMess age(Message& m)
à System.Windows.Forms.Application.ThreadContext.Pro cessFilters(MSG& msg, Boolean& modified)
à System.Windows.Forms.Application.ThreadContext.Pre TranslateMessage(MSG& msg)
à System.Windows.Forms.Application.ThreadContext.Sys tem.Windows.Forms.UnsafeNativeMethods.IMsoComponen t.FPreTranslateMessage(MSG& msg)
à System.Windows.Forms.Application.ComponentManager. System.Windows.Forms.UnsafeNativeMethods.IMsoCompo nentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
à System.Windows.Forms.Application.ThreadContext.Run MessageLoopInner(Int32 reason, ApplicationContext context)
à System.Windows.Forms.Application.ThreadContext.Run MessageLoop(Int32 reason, ApplicationContext context)
à System.Windows.Forms.Application.Run()
à NinjaTrader.NTMain.Main()

[NinjaTrader_Bertrand]

Thanks Gomi, could reproduce here - we will look into matters.

[NinjaTrader_Bertrand]

Thanks again for the report Gomi to us - development is looking to apply a fix for our next major NT update for this item.