Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Ask Me Anything (AMA) with NinjaTrader Client Services
City Index is INTL brand, GAIN is domestic. Yes, NT can be run side-by-side with TOS with single logon.
Disclosure: This communication is sent to you by NinjaTrader, LLC, a software development company which owns and supports all proprietary technology relating to and including the NinjaTrader trading platform.
Disclosure: This communication is sent to you by NinjaTrader, LLC, a software development company which owns and supports all proprietary technology relating to and including the NinjaTrader trading platform.
Will NinjaTrader fix Memory Leak in Strategy Analyzer?
There is an issue of a memory leak in the Strategy Analyzer Optimizer that has been confirmed by support using SampleMACrossover Strategy in Safe mode. This means it is inherent in the NinjaTrader platform code.
It causes a resource exhaustion error with Committed and Working memory maxing out past the RAM in my case past 32 GB. This condition kills NinaTrader. One then has to restart. This memory leak makes the functionality of the Optimizer non-functional for any large optimization due to the fatal error.
Here is a picture of the resource monitor before and during an optimization.
I have submitted this issue on the support forum.
I have noticed memory leak issues in Strategy Analyzer in NT8 go back to 2015 on the support forum, all unresolved:
There does not seem to be any resolution to any of these posts concerning the memory leak in the Strategy Analyzer.
5 years of the same problem going unsolved. Many of the posters have given NT possible solutions for fixing this memory leak. Garbage collection with NET framework can be done. Microsoft uses NET and manages to collect garbage.
I have a significant project and have invested a lot of money into development that requires NinjaTrader.
Is NinjaTrader going to be serious about fixing this critical item of fundamental functionality? I need to know and make plans for my project. NinjaTrader has tremendous potential for a strategy trading platform. That is why I chose it. But that tremendous potential is wasted if this memory leak is not fixed. It means the real functionality of trading the futures markets with strategies using NinjaTrader is non-functional, and fatal.
Ray, can you personally oversee this to make sure it gets properly resolved? I need feedback for planning.
Why doesn't Ninja have a public facing issue and feature request tracker (items reported by customers, not internal items)?
Currently, you post into the support forum, and if you are lucky you get a response back with a tracking number and instructions to watch the release notes to see if it ever gets in. Support also talks about adding peoples votes to items. Again, kind of a joke, as you have items in the "list" that are many years old and have hundreds of votes, and will never see the light of day. Your current method is a convenient way to bury items and have no accountability.
It's ok that some items may be difficult or impossible to implement, just document that in the item so we know instead of hoping that maybe someday it will happen. If you were listening to your customers, you would provide that list and allow users to have maybe five votes that they can spread around. And of course, then use that list to fix/add items.
The last item mentioned in this thread about the memory leak is crazy. It makes the feature completely unusable. This should be a trivial item for your team to fix since it is 100% reproducible with Ninja only code.
