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)
From what you are experiening (high memory usage and indy crash), you are most probably encountering a memory leak caused by some indicator.
If the only indicator on your chart is the profile, then the profile is the cause, the only solution can come from the author correcting his code.
What you wrote sounds very plausible and you maybe right. However, could it not be that the underlying architecture (in this case the multi threading architecture) of NinjaTrader handles requests in a less efficient way? As is stated by some indicator vendors. An indicator depends on the underlying technology.
It seems it happens when extensive drawings are used. Could it not be a combination of things, I mean NinjaTrader, .Net and the indicator, maybe in combination with the NVIDIA Graphics driver?
I think it must be possible to locate and fix the problem when NinjaTrader, Indicator vendors and users work together.
The problem, with a sound & clear error message, is reported more often before but all threads on this topic ended up dead without a solution.
What I will do is this: I will try the work around ( from Sim22) with starting & ending NT with a naked Workspace for a while.
After that I will start NT with my regular Workspace. I expect to see the "Chart Rendering Failed"-message in the log again and increasing memory usage till the computer will become unresponsive. Then I will be able to reproduce it and the problem will likely be caused by rendering of the historic- and real-time data ( rancho post 1). If the problems arise while using the work around it will likely been caused by memory leaks (as Gomi stated above).
There still could be other causes. If I am not mistaken Sim22 is 'investigating' if the problem can be caused by NVIDIA (and DirectX rendering issues).
I received notice from NinjaTrader yesterday. They confirmed they were looking into the issue. Hopefully we can get this resolved. I will keep you posted.
Last week I had no crashes or problems at all. I start and end every session with naked charts (Minute- and Tick charts without any indicator), let the data load and then switch to my regular workspace with indicators. If I make a change to my chart I will first disconnect. As said, no problems since then.
This week I will skip the naked chart startup and will use only my regular workspace to see if problems will return.