Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 16 Jun 2024 07:43:08 +0000
[Locked] - Abnormal Shutdown of Sierra Chart when Modifying Order
View Count: 1465
| [2021-03-10 23:07:28] |
| |
|
We have a few, about a total of two or three reports of when a user modifies an order in Sierra Chart, they get an immediate shutdown in some cases. This is the prior thread on this subject: Notice: Stack Overflow Issue Our conclusion, at that time, was at this was some operating system level issue. While that seems unlikely, that was all that we could reasonably conclude. We could never reproduce the issue even with extensive work. We will continue to look into the issue to determine the cause. But we need more information from users when it happens. In the threads about this issue, we have asked for that information. Obviously Sierra Chart is a very high quality software, and it is designed to be very stable and reliable. It is one of the best quality programs in the world in all categories. And we make that statement with confidence. While sometimes there are issues and there certainly a lot of room for improvement as we clear out these Microsoft dialogs and things like that, still it is very good quality and stable software. So this issue, is not consistent with the quality and experience that users are used to, so it is obviously very concerning but at the same time the problem is not reproducible by us. And there is a possibility that there it is something specific to these users system or configuration leading to the problem. We have very high standards, and this is why we can be critical with external services when they do not work well in some ways, and we get burdened with a lot of support questions related to those issues. We will do our best to isolate and resolve the issue to the extent possible. It does seem like it is something we should be able to resolve but at the same time if it is, we should be able to reproduce it and we just cannot. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2021-03-10 23:08:44] |
| |
|
There are couple of things that we are looking at related to this, both today and tomorrow. So be assured, we are on top of the problem. But if we cannot reproduce it or find anything, then it is also not getting resolved either. Although as we look closer and closer we do find areas of improvement and we are making those. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2021-12-22 16:33:36] |
| |
|
We want to update this thread and let users know, that we believe we determined what the issue was, and it was resolved about 3 to 4 months ago. Basically we reduced the amount of stack space used when modifying an order. It was not very much. We do not remember the exact number but certainly it was less than 32K. Not very much. It was clear there was a stack corruption occurring and why the extra stack space was leading to an issue we do not know. But once we reduced it, the problem has gone away. We never did identify any stack corruption issue in our code. What has happened, is that over the years, as the order data structure has grown, and as more functionality was added to Sierra Chart, this has caused the stack space to increase. But we made changes to remove all of this additional stack space being used. The only logical conclusion, is that this was the fault of compiler optimizations and there was some faulty code that the compiler was perhaps generating which was causing an issue with a larger stack space. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2021-12-22 17:02:16
|
To post a message in this thread, you need to log in with your Sierra Chart account: