Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

NT DLL teardown issue

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

    NT DLL teardown issue

    Hello,

    I found an issue when using NT DLL with eSignal EFS. At the beginning I thought it was an eSignal EFS engine issue, therefore I posted my report on eSignal's forum. Now Jason at eSignal pointed out the issue was caused by NT DLL teardown function which is called within postMain(). Can someone from NinjaTrader take a look at it?




    - Clearpicks

    #2
    What's the issue? Why would you want to call TearDown explicitely?

    Comment


      #3
      I don't know how NT DLL releases the resource it is using. When I change the symbol or interval of an eSignal chart, basically the EFS is reloaded. When I close an eSignal chart, the EFS is unloaded. In both cases, I want to make sure the resources used by the NT DLL is released before the NT DLL object is destructed. The only function in efs would be called when EFS is exiting is postMain(). So I added NT DLL teardown() in postMain(). Is this the correct way and place to call teardown()? If not, what would happen if I frequently change symbol and interval of a chart on which an EFS using NT DLL is running?

      - Clearpicks

      Comment


        #4
        Only call TearDown as the DLL is "unloaded". Since you can't control that (since you don't have access to the eSignal source code) -> don't call TearDown.

        Just go by the eSignal sample provided which does not call TearDown.

        Comment


          #5
          The issue is calling NT DLL teardown() within eSignal EFS postMain() may result in eSignal EFS engine printing out an error message as in this screenshot.



          - Clearpicks

          Comment


            #6
            If it is a static scenario (once the EFS (with NT DLL) starts running, it keeps running untill eSignal is closed), there obviously is no problem. However what if the symbols or interval of the chart is frequently changed, which is equivalent to an NT DLL object is created every time the chart symbol or interval is changed, would this cause performance issue after esignal running for a while when too many NT DLL objects being created?

            - Clearpicks

            Comment


              #7
              >> when too many NT DLL objects being created
              There is no such issue. Just go with the sample.

              Comment


                #8
                Thank you.

                Comment

                Latest Posts

                Collapse

                Topics Statistics Last Post
                Started by Jonker, Today, 01:19 PM
                0 responses
                1 view
                0 likes
                Last Post Jonker
                by Jonker
                 
                Started by futtrader, Today, 01:16 PM
                0 responses
                5 views
                0 likes
                Last Post futtrader  
                Started by Segwin, 05-07-2018, 02:15 PM
                14 responses
                1,791 views
                0 likes
                Last Post aligator  
                Started by Jimmyk, 01-26-2018, 05:19 AM
                6 responses
                844 views
                0 likes
                Last Post emuns
                by emuns
                 
                Started by jxs_xrj, 01-12-2020, 09:49 AM
                6 responses
                3,295 views
                1 like
                Last Post jgualdronc  
                Working...
                X