Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Fri, 03 May 2024 03:44:52 +0000
2041 2nd Instance Crashing (formerly "Code Breaking Changes")
View Count: 759
| [2020-07-24 04:05:28] |
| User462086 - Posts: 188 |
|
Can you please confirm, if any, code breaking changes in 2041? I've just upgraded & can't open a chartbook in a second instance without using 'Safe Mode', otherwise the instance crashes. I'm assuming this is due to a change that affects my custom studies, which have been stable for almost a year and were used yesterday on v2040 without issue. I've already read through the following link so I understand this may very well be my own coding error now coming to light. Nonetheless, if something has changed in 2041, knowing about it would greatly reduce the amount of time required to fix it. Sierra Chart Unexpectedly Shutting Down | Memory Errors | Unusual Software Problems | Exception Errors | Freezing of User Interface Many thanks!! |
| [2020-07-24 04:43:23] |
| User462086 - Posts: 188 |
|
The custom studies are stable in the main instance so there are no code breaking changes. I'll test the chartbook in the main instance and report back after today's session.
|
| [2020-07-24 04:45:54] |
| |
|
There should not be any changes which would cause problems with custom studies. At least we are not aware of any and in general there should never be a problem like this unless we document it ahead of time.
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 |
| [2020-07-25 04:51:56] |
| User462086 - Posts: 188 |
|
The chartbook opened without issue in the main instance, and in the 2nd instance today. Markets are closed at the moment. Whatever the problem was it appears to have resolved itself.
|
To post a message in this thread, you need to log in with your Sierra Chart account: