JRHKM
01-07-2011, 08:20 PM
This concerns NinjaTrader 7.0.1000.1.
NinjaTrader unexpectedly goes into a long-running internal state in certain situations when you have both Historical Data Manager and Instrument Manager open at the same time.
Steps to reproduce:
1. Open Historical Data Manager and click on the Edit tab.
2. Open Instrument Manager.
3. Open one or more instruments in Instrument Manager for editing.
4. Make some changes to the symbol mapping on the Misc tab.
5. Click okay to close the instrument dialog.
6. Click okay to close Instrument Manager.
NinjaTrader goes into a long-running internal state that uses up a large amount of CPU. I think what is happening is that it is cycling through all the instruments displayed in Historical Data Manager's treeview to apply changes made in Instrument Manager. But is it necessary for it to go through all the instruments? In one case I made only a single mapping change to a single instrument and it still ran for over a minute.
NinjaTrader unexpectedly goes into a long-running internal state in certain situations when you have both Historical Data Manager and Instrument Manager open at the same time.
Steps to reproduce:
1. Open Historical Data Manager and click on the Edit tab.
2. Open Instrument Manager.
3. Open one or more instruments in Instrument Manager for editing.
4. Make some changes to the symbol mapping on the Misc tab.
5. Click okay to close the instrument dialog.
6. Click okay to close Instrument Manager.
NinjaTrader goes into a long-running internal state that uses up a large amount of CPU. I think what is happening is that it is cycling through all the instruments displayed in Historical Data Manager's treeview to apply changes made in Instrument Manager. But is it necessary for it to go through all the instruments? In one case I made only a single mapping change to a single instrument and it still ran for over a minute.