Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

Indicator Coding Error Intermittently Crashes NT 8.

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

    Indicator Coding Error Intermittently Crashes NT 8.

    Found Indicator coding eror that intermittently crashes NT 8.0.0.5 64-bit (Multi-Broker) - BETA. Have reduced the error to simplest example which is attached. The statement which causes the crash is:

    Code:
    [B]return string.Format("{[COLOR=Red]1[/COLOR]}", Name);[/B] in  
    
            public override string DisplayName
            {   
                get {
                     return string.Format("{1}", Name);
                }    
            }
    I saw the first NT crash in code I was working on. Indicator was in a Workspace chart. After Indicator compiled NT crashed.

    The attached example has also crashed NT. Have not been able to determine what conditions cause intermittent crash of NT.

    Attached screenshot is from test when NT did not crash.
    Attached Files

    #2
    Just remembered something about the first crash that happened. I created a new Workspace and added Chart with Indicator that I was testing. Did not save new Workspace. Made change to string.Format that introduced error resulting in crash.

    There had been 4 values to insert and I removed the third value but left the insertions as {0} {1} {3}. Compile did not detect error. When compile finished NT crashed. Don't remember if I closed Editor before crash. Restarted NT and had to create Workspace again and probably saved it.

    Not sure, but crash of attached example may have also happened with unsaved Workspace.

    Too late for me to start testing again tonight. Hope that this helps.
    Last edited by Jim W.; 10-19-2015, 07:46 AM.

    Comment


      #3
      Hello Jim W.,

      Thanks for your post.

      I tried to replicate the crash on both 8.0.0.5 and the continuous build using the steps provided and can only generate the error message.

      If possible please send in your log and trace files for the date and identify the approximate time of the crash(es). Send the log and trace files to Platformsupport[at}Ninjatrader[dot]com atten: Paul and the title of this thread.

      On the other hand if you can repeatedly reproduce, please advise the steps involved.

      Thanks for the time to advise of this.
      Paul H.NinjaTrader Customer Service

      Comment


        #4
        Paul, I was able to create the crash on my first attempt. Here is exactly what I did, nothing left out:

        1) Open NT8 8.0.0.5 64-bit (Multi-Broker) - BETA
        2) Start NinjaScript Editor
        3) Selected Indicator CrashNT8 from earlier attachment.
        4) Change line 59 removing the error.
        return string.Format("{1}", Name);
        Replaced line with
        return string.Format("{0}", Name);
        5) Compiled CrashNT8 and exited editor.
        6) Closed all Workspaces except one that I call Empty, which is empty of all Charts etc..
        7) Created new workspace called CrashNT8-Oct19
        8) Created a chart in workspace for ES called ES Chart and selected ES 12-15.
        9) Added Indicator CrashNT8 to chart.
        10) At this point Workspace has not been saved. Started New NinjaScript Editor.
        11) Selected Indicators then selected Indicator CrashNT8.
        12) Changed line 59, replacing "0" with "1".
        13) Compiled no errors.
        14) Exited Editor.
        15) Started Continuum Connection.
        16) Took hands off keyboard.
        17) Heard gongs sound indication Continuum Connection made.
        18) About a second after gong sound NT Window disappeared.

        Associated Log:
        2015-10-19 20:00:53:870|2|4|Session Break (Version 8.0.0.5)
        2015-10-19 20:00:54:975|1|4|Verifying license at primary server...
        2015-10-19 20:00:55:678|1|4|Type = Simulation State = Verified Start Date = 12/31/2004 End Date = 11/30/2099
        2015-10-19 20:00:55:739|1|4|Global simulation mode enabled
        2015-10-19 20:00:56:237|1|4|Vendor assembly 'JigsawToolsNT8' version='5.2.9.6' loaded.
        2015-10-19 20:00:56:237|1|4|Vendor assembly 'PriceSquawkV4' version='4.5.0.0' loaded.
        2015-10-19 20:00:56:237|1|4|Vendor assembly 'System.Drawing' version='4.0.0.0' loaded.
        2015-10-19 20:00:56:860|1|2|Connecting to IS server (HDS9.NinjaTrader.com/31658)
        2015-10-19 20:00:56:868|1|4|Automated trading disabled
        2015-10-19 20:00:57:008|1|32|Order entry hot keys disabled
        2015-10-19 20:00:57:009|1|4|Auto close enabled=False
        2015-10-19 20:19:24:006|1|2|My Continuum: Primary connection=Connecting, Price feed=Connecting
        2015-10-19 20:19:38:357|1|2|My Continuum: Primary connection=Connected, Price feed=Connected
        2015-10-19 20:19:38:395|1|2|Time to auto close position='12:00:00 AM', Enabled=False
        2015-10-19 20:19:38:411|1|2|Connecting to HDS server (HDS9.NinjaTrader.com/31655)
        2015-10-19 20:19:40:133|0|4|Unhandled exception: Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
        2015-10-19 20:19:40:260|3|16|Chart rendering failed. There is likely a problem with a chart object's OnRender method. D2D error = 'Index (zero based) must be greater than or equal to zero and less than the size of the argument list.'
        2015-10-19 20:19:40:262|3|16|Chart rendering failed. There is likely a problem with a chart object's OnRender method. D2D error = 'Index (zero based) must be greater than or equal to zero and less than the size of the argument list.'
        2015-10-19 20:19:40:264|3|16|Chart rendering failed. There is likely a problem with a chart object's OnRender method. D2D error = 'Index (zero based) must be greater than or equal to zero and less than the size of the argument list.'
        End of log
        Last edited by Jim W.; 10-20-2015, 01:00 AM.

        Comment


          #5
          Hello Jim W.

          Thank-you for the time and effort.

          I have been able to replicate on the continuous build.

          It seems to reduce down to:
          1) Add the correctly coded indicator to the chart
          2) In an editor create the error condition in the indicator {1}, successfully compile
          3) reload the indicator on chart - Poof, crashed NT8,

          I will submit this to development and will update this thread when I have further information.

          Thanks again for your efforts to help us with the beta testing.
          Paul H.NinjaTrader Customer Service

          Comment


            #6
            My observation is that if no Connection then no crash. Crash occurs when Connection becomes connected or was connected before compile.

            Comment

            Latest Posts

            Collapse

            Topics Statistics Last Post
            Started by timmbbo, Today, 08:59 AM
            1 response
            2 views
            0 likes
            Last Post NinjaTrader_ChelseaB  
            Started by KennyK, 05-29-2017, 02:02 AM
            2 responses
            1,280 views
            0 likes
            Last Post marcus2300  
            Started by fernandobr, Today, 09:11 AM
            0 responses
            2 views
            0 likes
            Last Post fernandobr  
            Started by itrader46, Today, 09:04 AM
            1 response
            6 views
            0 likes
            Last Post NinjaTrader_Clayton  
            Started by bmartz, 03-12-2024, 06:12 AM
            5 responses
            33 views
            0 likes
            Last Post NinjaTrader_Zachary  
            Working...
            X