Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Mon, 29 Apr 2024 04:58:40 +0000
Recent Releases Crashing
View Count: 939
| [2017-02-23 01:42:47] |
| User948528 - Posts: 108 |
|
Just upgraded to 1522 Current Release, crashed on closing a chartbook, Message Log does not seem to indicate cause, Windows 10 error dialog attached. 1518 seemed to work fine. Prior to that, other recent Current Releases above 1500 had been crashing also. I use only Current Releases rather than Pre-Releases hoping to prevent issues like this. Prior to 1500s, have never had SC crashes in many years of use. Date Time Of Last Edit: 2017-02-23 01:46:15
|
 2017-02-22_20h38_20.png / V - Attached On 2017-02-23 01:41:57 UTC - Size: 6.21 KB - 220 views |
| [2017-02-23 02:47:36] |
| |
|
We are aware of some issues in recent releases but there should not be any trouble with version 1522. This is the first report we have a problem with this version. If you are running custom studies, refer to help topic 17: Https://www.sierrachart.com/index.php?page=doc/helpdetails17.php If help topic 17 does not help you, then for the time being go back to 1518. 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 |
| [2017-02-23 03:02:48] |
| |
|
Another thing you can do is attach your Chartbook and we can test it and see if we see the same problem. Here are instructions: https://www.sierrachart.com/index.php?page=PostingInformation.php#AttachFile 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 |
| [2017-02-23 05:42:17] |
| |
|
Is the only time you are encountering this problem is when Sierra Chart is exiting? We noticed this as well on a connection that is using Google protocol buffers which is also being used for CQG. We strongly suspect the problem is within the Google protocol buffer library which is developed by Google. We are using a new version of that library and it may have a 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2017-02-23 19:25:25] |
| |
|
We want to determine the reason for the problem. Can you let us know if you are running custom studies? And if you have tried using Safe Mode? If you are still having a problem we would like you to update to the Prerelease following the instructions here: http://www.sierrachart.com/index.php?page=doc/download.php#FastUpdate This will be version 1523. We made a change in 1523 which may solve the problem of an error on shutdown. It relates to background lingering of a network socket connection and the overlapped I/O buffer getting destroyed before the socket is closed. 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 |
| [2017-02-23 20:08:31] |
| User948528 - Posts: 108 |
|
This was on Rithmic, I am using custom studies. This time the crash happened simply while closing only one open chartbook, did not shut down SC fully. The other times on recent releases seemed to have been while doing simple random actions, not aware of a pattern. The custom studies are integral to my trading, have been using them for a long time without issues prior to recent releases. The crashes are quite rare, so that it would be difficult to test/debug or check each study. I am back on 1518 for the time being, if it reoccurs again in the future, will try to pinpoint further. Attached the CB believe was being used at time of crash, unfortunately it is a complex CB with many charts and studies. Date Time Of Last Edit: 2017-02-23 20:29:59
|
Private File |
| [2017-02-24 04:07:29] |
| |
|
If you are using custom studies, we believe that is the reason for the problem on the latest version 1522 and also if you experience it on 1523. You need to use Safe Mode to rule those out as a problem. We will look at the Chartbook if we need to. But we have no other reports of a problem. We recommend you recompile/rebuild the custom studies on 1522. 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 |
| [2017-02-28 17:54:44] |
| User948528 - Posts: 108 |
|
Tried 1523, got a different crash, seems of DTCBridge, log and error attached. Going through each custom study/rebuilding will be too difficult for me, will be sticking to 1518/last stable build for now. Date Time Of Last Edit: 2017-02-28 17:56:38
|
2017-02-28_12h40_05.png / V - Attached On 2017-02-28 17:52:43 UTC - Size: 7.23 KB - 223 views  dtccrash.txt - Attached On 2017-02-28 17:56:35 UTC - Size: 5.26 KB - 228 views |
| [2017-02-28 18:32:19] |
| |
|
Please understand that an abnormal shutdown of the Rithmic bridge program is completely unrelated to this. That issue is almost certainly going to be with the Rithmic software itself which we have no control over. This problem can occur with any version of Sierra Chart. This is unusual to encounter it though but if you want to avoid it, you will need to not use Rithmic. There is no other choice. It is not something we can help with. We recommend CQG or CTS: http://www.sierrachart.com/index.php?page=doc/Data.php 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 |
| [2017-03-26 15:08:48] |
| User948528 - Posts: 108 |
|
No changes to custom studies, original issue seems resolved on 1523, no further crashes.
Date Time Of Last Edit: 2017-03-26 15:08:56
|
| [2017-03-26 20:24:11] |
| |
|
We think this is only coincidental and you can still have problems. We do think the problem is in the custom study you are using. What you are describing makes sense because memory corruptions or other problems could cause a problem in one version and not another. They are random in their behavior. 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: 2017-03-26 20:27:34
|
To post a message in this thread, you need to log in with your Sierra Chart account: