Multi symbol chart does not load all hist data

[aslane]

I have a chart that has two instruments on it. The first panel contains a futures contract (ES 03-09) in which the data comes from ZenFire. The second panel has ^TICK, and the data is provided via IB (multi-broker license). The time frame is a 30 sec chart.

If I connect to Zen, the futures data is properly loaded. When I then connect to IB, the ^TICK data is only updated from the current time forward (i.e. if I connect 30 min into session, I am missing first 30 min of data).

If I then reload all historical data on that chart, the chart effectively hangs - Ninja is still running fine, status msg in control center says it is loading data from Zen, all of my memory gets used up, take an OutOfMemoryException, and finally get a popup saying: "Failed to unzip server data: System.OutOfMemoryException............"

The instruments are setup to only have two days of data, so it is not a size issue.

Update: Ninja had to be restarted after the above. I also noticed that there was an IB pacing violation earlier in the session for a different symbol. May be related, but still should not consume memory and crash.

[NinjaTrader_Ray]

Thanks for reporting, we will look into the exception. On the missing data from IB, this is expected. Second(s) charts use tick data. IB does not provide historical tick data thus nothing is loaded and bars are only built using real-time data.

[aslane]

Thanks, I had forgotten about IB's lack of tick hist data, and it jives with what I see on other charts.

[NinjaTrader_Austin]

aslane, I followed the instructions you posted but was unable to reproduce the error. I started NT, created the chart with ES 03-10 on top and ^TICK on bottom, connected Zen (ES loaded fine and started updating without a problem), and connected to IB where ^TICK started updating fine as well. Then I reloaded all historical data and NT correctly retrieved the data and the charts continued to function properly. There were no memory exceptions or anything.

Is there anything else about your setup that could be affecting your NT and causing the error?

[aslane]

Well, I have a lot of stuff on the workspace that failed, but everything else was running fine with low mem utilization before creating the failing window.

I have seen similar fails when it is on a simple workspace, and it has something to do with initial creation, as once I have a window saved in the workspace it seems to work the next time I start NT.

I will try to narrow it down further.