Tweet
The problems we developers are having with ReleaseHistory and ReleaseSymbol have been discussed here ad nauseum. Anyone can develop an app that tracks and properly releases handles as suggested, but during development, crashes, breakpts, faulty logic, and more importantly CONSTANT ESIGNAL CRASHES, often leaves me in an unknown state with regard to open handles.
ESignal then fails to return historical data on subsequent calls to RequestHistory for some symbols. (Because there is a previous open handle for the symbol??)
1.) HOW CAN I RETURN TO A KNOWN STATE?
Simply restarting eSignal and the data manager does not fix the problems, so their is some persistence in a database file or something. Resetting the DB manually from the Data Manager's Symbols window does not help.
2.) WHAT IS WRONG WITH SIMPLY LOOPING FROM 1 TO 500 AND CALLING RELEASEHISTORY FOR EVERY POSSIBLE HANDLE DURING AN APP'S INITIALIZATION?
It does not always help and sometimes seems to set the stage for a later eSignal crash.
Please don't refer me to the previous thread explanations of this problem - I've read them all. They are well-intended, but I need practical advise other than "keep track of your handles."
ESignal then fails to return historical data on subsequent calls to RequestHistory for some symbols. (Because there is a previous open handle for the symbol??)
1.) HOW CAN I RETURN TO A KNOWN STATE?
Simply restarting eSignal and the data manager does not fix the problems, so their is some persistence in a database file or something. Resetting the DB manually from the Data Manager's Symbols window does not help.
2.) WHAT IS WRONG WITH SIMPLY LOOPING FROM 1 TO 500 AND CALLING RELEASEHISTORY FOR EVERY POSSIBLE HANDLE DURING AN APP'S INITIALIZATION?
It does not always help and sometimes seems to set the stage for a later eSignal crash.
Please don't refer me to the previous thread explanations of this problem - I've read them all. They are well-intended, but I need practical advise other than "keep track of your handles."
Comment