Support Board
Date/Time: Sat, 28 Mar 2026 14:50:42 +0000
Post From: Notice: CME Denali Data Feed Intermittent Data Delay January 26-February 6, 2026
| [2026-02-09 18:20:57] |
| Sierra_Chart Engineering - Posts: 23359 |
|
We do not want to come to any definite conclusions at this point in time, but we believe, the source of the issue, which was a processing inefficiency in one or more locations, is the fact that STL containers, do not actually release memory when cleared. Thinking about it, the very fact that we call a clear function on a STL container and it does not actually release memory, is a design flaw. Not releasing memory can have its advantages. Therefore, the clear function needs to have a parameter, specifying whether or not to release memory. The fact that this does not exist is dumb. And the fact that these containers also throw exceptions, due to memory allocation failures is another dumb thing. This only goes to show, why we just cannot trust anyone. What we have learned over the decades is to do everything ourselves and trust no one. The fault has been STL. Well we have learned something. And we are not going to be using STL any longer, for lookup of symbol data objects. This further, just simply emphasizes that the concept of managed code, and higher-level languages like C#, really put you in a category of substandard software. This is why Sierra Chart is and will always be unmanaged native C++ code. And why programs like ninja trader, have a massive disadvantage and will never be able to overcome it. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2026-02-09 19:45:19
|