Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

FYI - The Control Center and NinjaScript Output windows dead locked

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    FYI - The Control Center and NinjaScript Output windows dead locked

    I little background on what I was doing. I was looking at the WaveTrendV2 indicator, from the App Share, and reviewing the code. I added some simple Print() statements so I could review some data on the Output window. I customized the indicator colors and saved a default indicator template. After that I added the native Drawing Tool Tile indicator to the chart, so I could mark things. So after customizing the chart, not the chart Properties, I went to the Control center and saved the workspace, and that is when the Control Center and Output window locked up. The chart and NinjaScript Editor were still working fine.
    Other info
    • There were three other workspaces open in the background not being used. The Untitled had nothing, and the other two workspaces had about 4 charts in each workspace.
    • The data feed was connected, but there is no data on Saturdays.
    • As I'm writing this I noticed the memory usage for Ninja is continuously climbing about 1MB every couple of seconds. It has reached 4,900MB.
    I doubt this is reliably recreatable, so no need to write back unless you'd like more info.

    #2
    Hello zacharydw00,

    I didn't find in the User App Share section of the NinjaTrader Ecosystem. Have you contacted the author of the script to report the behavior?
    https://ninjatraderecosystem.com/use...ch=WaveTrendV2

    If the script is accessing the UI thread, the most often reason this happens is due to using Dispatcher.Invoke() instead of .InvokeAsync().
    https://ninjatrader.com/support/help...-threading.htm
    https://ninjatrader.com/support/help...collection.htm

    Climbing memory may indicate a broken loop or logic that is causing recursion.

    I would recommend debugging the script to find where the issue is coming from. (Including confirming if a documented NinjaScript method is causing an issue)
    https://ninjatrader.com/support/foru...121#post791121
    Chelsea B.NinjaTrader Customer Service

    Comment


      #3
      Hi Chelsea,
      I've attached the indicator in case you are curious. It may have come from Futures.io. It's just another common oscillator spin-off. Just the simplest of Ninjascript coding. No UI threading, or SharpDX. I doubt this indicator could be the cause. As mentioned before, I think this is a random fluke.
      Thanks
      Attached Files

      Comment


        #4
        I found the Wave Trend indicator. The name of the listing should be changed to match the indi. name displayed on the chart.
        https://ninjatraderecosystem.com/use...-oscillator-2/

        Comment


          #5
          Hello zacharydw00,

          Have you reported the behavior to the author that has uploaded this script?

          You have mentioned you added prints. Is there a specific line of code that is causing this behavior to be reproducible?
          Chelsea B.NinjaTrader Customer Service

          Comment

          Latest Posts

          Collapse

          Topics Statistics Last Post
          Started by Renorail, Today, 01:38 PM
          1 response
          5 views
          0 likes
          Last Post Renorail  
          Started by BrianARice, Today, 01:16 PM
          0 responses
          5 views
          0 likes
          Last Post BrianARice  
          Started by Ousher, Today, 09:08 AM
          0 responses
          6 views
          0 likes
          Last Post Ousher
          by Ousher
           
          Started by Unsuitable, Today, 08:41 AM
          0 responses
          14 views
          0 likes
          Last Post Unsuitable  
          Started by newdill, Today, 07:54 AM
          0 responses
          7 views
          0 likes
          Last Post newdill
          by newdill
           
          Working...
          X