Ever since I started using NT8, it runs fine on small jobs that take only a few minutes, but tends to crash after it has run for 5-10 minutes. Windows Task Manager generally shows NinjaTrader using 1.2-1.4 GB of RAM while there is usually 2-6 GB of RAM free (total of 12 GB). It does not seem to matter whether I have been running a lot of applications or whether I have done a restart and run NinjaTrader only.
Following is an example:
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: NinjaTrader.exe
Problem Signature 02: 8.0.0.8
Problem Signature 03: 568bf871
Problem Signature 04: mscorlib
Problem Signature 05: 4.6.1055.0
Problem Signature 06: 563c0eac
Problem Signature 07: 12bc
Problem Signature 08: 0
Problem Signature 09: System.OutOfMemoryException
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
The System.OutOfMemoryException is sometimes thrown by NinjaTrader.core instead of mscorlib. Occasionally, System.NullReferenceException is thrown first:
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: NinjaTrader.exe
Problem Signature 02: 8.0.0.8
Problem Signature 03: 568bf871
Problem Signature 04: NinjaTrader.Core
Problem Signature 05: 8.0.0.8
Problem Signature 06: 568bf86e
Problem Signature 07: fe1
Problem Signature 08: 37c
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
In debug mode, System.OutOfMemoryException was thrown by the last (“else”) call to AddBar() in MinuteBarsType.OnDataPoint(), although the debugger showed bars.Count == 0, so that branch should not have executed (see first attachment).
Running the same job again in debug mode, System.OutOfMemoryException was thrown by the call to EnterLong() in SampleMACrossover.OnBarUpdate(), although the debugger showed this.Bars and this.Instrument were both null (see first attachment), even though the job had been running for several minutes. I don’t understand how OnBarUpdate() could be called if this.Bars is null.
Please let me know if you need more information.
NT8 has nice feature improvements, but I can’t trade with it until it becomes more stable.
Comment