NexusFi: Find Your Edge


Home Menu

 





NT8 with NinZA MP: Chart rendering failed


Discussion in NinjaTrader

Updated
      Top Posters
    1. looks_one Miesto with 8 posts (1 thanks)
    2. looks_two gomi with 3 posts (7 thanks)
    3. looks_3 JonnyBoy with 2 posts (0 thanks)
    4. looks_4 KahunaDog with 1 posts (0 thanks)
    1. trending_up 5,528 views
    2. thumb_up 9 thanks given
    3. group 6 followers
    1. forum 15 posts
    2. attach_file 2 attachments




 
Search this Thread

NT8 with NinZA MP: Chart rendering failed

  #11 (permalink)
 gomi 
Paris
Market Wizard
 
Experience: None
Platform: NinjaTrader
Posts: 1,270 since Oct 2009
Thanks Given: 282
Thanks Received: 4,505

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.

Reply With Quote
Thanked by:

Can you help answer these questions
from other members on NexusFi?
New Micros: Ultra 10-Year & Ultra T-Bond -- Live Now
Treasury Notes and Bonds
Futures True Range Report
The Elite Circle
Deepmoney LLM
Elite Quantitative GenAI/LLM
ZombieSqueeze
Platforms and Indicators
Exit Strategy
NinjaTrader
 
Best Threads (Most Thanked)
in the last 7 days on NexusFi
Get funded firms 2023/2024 - Any recommendations or word …
61 thanks
Funded Trader platforms
39 thanks
NexusFi site changelog and issues/problem reporting
26 thanks
GFIs1 1 DAX trade per day journal
18 thanks
The Program
18 thanks
  #12 (permalink)
 Miesto 
Monte Carlo, Monaco
Legendary Market Wizard
 
Experience: Advanced
Platform: NinjaTrader 8
Broker: NinjaTrader Brokerage
Trading: Futures
Posts: 629 since May 2012
Thanks Given: 779
Thanks Received: 1,150


gomi View Post
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.

Bonjour Gomi,

Thanks for writing in (on the topic ).

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.

Visit my NexusFi Trade Journal Started this thread Reply With Quote
  #13 (permalink)
 gomi 
Paris
Market Wizard
 
Experience: None
Platform: NinjaTrader
Posts: 1,270 since Oct 2009
Thanks Given: 282
Thanks Received: 4,505


As you may know, I did create a volume profile for NT8 too, it also does heavy drawing, and it does not leak memory.

In Windows, graphical resources are unmanaged so it's the responsabilty of the programmer to free them when he's done using them.

If you forget one, and since drawing happen very frequently, you get memory leaks.


Reply With Quote
Thanked by:
  #14 (permalink)
 Miesto 
Monte Carlo, Monaco
Legendary Market Wizard
 
Experience: Advanced
Platform: NinjaTrader 8
Broker: NinjaTrader Brokerage
Trading: Futures
Posts: 629 since May 2012
Thanks Given: 779
Thanks Received: 1,150

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).

Visit my NexusFi Trade Journal Started this thread Reply With Quote
  #15 (permalink)
 Miesto 
Monte Carlo, Monaco
Legendary Market Wizard
 
Experience: Advanced
Platform: NinjaTrader 8
Broker: NinjaTrader Brokerage
Trading: Futures
Posts: 629 since May 2012
Thanks Given: 779
Thanks Received: 1,150


Mich62 View Post
I am afraid to be left in the dark as indicator vendors are pointing to NinjaTrader for a solution and NinjaTrader keeps pointing to the indicator vendors.

Here's the response from NinjaTrader:

"The best source of support and troubleshooting for custom NinjaScript would be the developer of the custom NinjaScript.

Please don't hesitate to contact me with any NinjaTrader questions.
"

They don't take any responsibility.

In the mean time people are struggling with NT8.

I don't think going back to NT7 is really an option. Neither is another charting program after all the costs I made for NT and the indicators.

So what to do?

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.

Visit my NexusFi Trade Journal Started this thread Reply With Quote
  #16 (permalink)
 Miesto 
Monte Carlo, Monaco
Legendary Market Wizard
 
Experience: Advanced
Platform: NinjaTrader 8
Broker: NinjaTrader Brokerage
Trading: Futures
Posts: 629 since May 2012
Thanks Given: 779
Thanks Received: 1,150


Mich62 View Post
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).

A short update.

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.

Visit my NexusFi Trade Journal Started this thread Reply With Quote




Last Updated on March 6, 2017


© 2024 NexusFi™, s.a., All Rights Reserved.
Av Ricardo J. Alfaro, Century Tower, Panama City, Panama, Ph: +507 833-9432 (Panama and Intl), +1 888-312-3001 (USA and Canada)
All information is for educational use only and is not investment advice. There is a substantial risk of loss in trading commodity futures, stocks, options and foreign exchange products. Past performance is not indicative of future results.
About Us - Contact Us - Site Rules, Acceptable Use, and Terms and Conditions - Privacy Policy - Downloads - Top
no new posts