Home >> Support Board

Support Board

Date/Time: Sun, 27 Oct 2024 08:30:59 +0000

How to Post a Message for Support

[Locked] - Stability Issue in Recent Sierra Chart Versions

View Count: 1241

[2024-06-26 20:51:49] #1 [Go To First Post]
Sierra_Chart Engineering - Posts: 16738
We are aware of a stability issue in newer versions, based on reports from users. The issue occurs when performing trading from Sierra Chart. We are not observing any problems ourselves, and hopefully only a small number of users are affected. We are working on this issue now. And if we do not get it resolved today we will remove the affected versions. We will post more information as soon as possible. And the affected versions. Although we can only go from what users are saying are the versions affected. 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

[2024-06-26 22:16:52] #2 [Go To First Post]
Sierra_Chart Engineering - Posts: 16738
We identified one problem from a user. The Relative Volume study does cause a small heap corruption. Most likely this is not something which would cause an issue but it can. It is the result of improper use of this function: sc.ClearAllPersistentData(); Update: Improper use of this function is calling this function, after establishing references to persistent variables within a study function. It must be called before establishing references to persistent variables within a study function. We have solved this in the Relative Volume study. Now we are looking into issues, involving trading and heap memory corruptions. 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: 2024-06-27 15:34:38

[2024-06-27 12:06:33] #3 [Go To First Post]
Sierra_Chart Engineering - Posts: 16738
We think we found the stability problem related to trading. And it should now be resolved in version 2651. To be released in less than 30 minutes. We do not want to make 100% statement that it is resolved until we have more time to review and consider this. This problem has existed for years, but it is something that normally would not cause any issue. And due to recent changes, it began to become apparent. The problem occurs when using the Move Stop to Breakeven functionality on Attached Orders. Once we are sure the issue is resolved we are going to recommend all users update to version 2651 or higher. The recent changes we did which caused the problem to become more apparent, related to this recent thread: Trading Keyboard Shortcuts Issue / Crashes System So those changes ultimately led us to the problem. 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: 2024-06-27 15:40:06

[2024-06-27 13:26:55] #4 [Go To First Post]
Sierra_Chart Engineering - Posts: 16738
Version 2651 has been released. 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

[2024-06-27 15:29:15] #5 [Go To First Post]
Sierra_Chart Engineering - Posts: 16738
The corruption issue involving trading definitely has been resolved. It relates to using Move to Breakeven functionality on Attached Orders. If you are not using this functionality you are not affected by the problem. If you are not using the Relative Volume study you are not affected by the problem with that study. If you are using the Relative Volume study or Move to Breakeven functionality on Attached Orders (Attached Orders: Move to Breakeven for Stop), then our advice, is to wait one day so we can be sure everything is fine with the latest version, and then update. Do not stay on an older version of Sierra Chart. 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

[2024-06-28 12:23:37] #6 [Go To First Post]
Sierra_Chart Engineering - Posts: 16738
We also want to comment, on the Crash Reporter program that Sierra Chart uses and the dump file. The dump file is a file, which is used by the Visual C++ development environment, for us to see exactly in the source code where a fault occurred. This is only more recent that this capability was added. Sierra Chart has always been very reliable software and there generally has not been a need for this. It was developed to troubleshoot an issue in our server environment in the past. The crash reporter and dump file, is something that we very rarely use internally ourselves. In this particular case of the issues in this thread, the dump file, if one was generated would have provided limited useful information because the fault was occurring, at a later point of when it actually happened. At least we think so. Probably. One user, gave us information from the event viewer showing that a heap corruption occurred. And that was enough information along with the Chartbook for us to troubleshoot one of the problems. What we do in cases like this, is we use an option on the debug heap under Visual C++ to keep memory allocations always allocated, and then we run checks in various area of the code to check the integrity of those and we can find heap corruptions very rapidly in this way. The point of all of the above, is the dump file and crash reporter is of generally minimal limited use to us. Also the procedure involved in working with a dump file is involved regarding matching the dump file to a particular revision. 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: 2024-06-28 12:24:05

To post a message in this thread, you need to log in with your Sierra Chart account: