Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Thu, 26 Sep 2024 23:33:41 +0000
SC Hangs when adding custom study
View Count: 1994
| [2013-11-12 03:29:04] |
| hairyMug - Posts: 31 |
|
1. add a custom study with inputs to chart 2. run bar-based backtest 3. change name of an input (in the study code) 4. recompile code 5. delete study from chart 6. try to add the study 7. SC hangs with following message: Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: SierraChart.exe Application Version: 700.0.0.0 Application Timestamp: 527ff702 Hang Signature: 86a2 Hang Type: 0 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Hang Signature 1: 86a291031dfa78c9345eaec1c8ceefb6 Additional Hang Signature 2: 4b95 Additional Hang Signature 3: 4b95ef3a28d29f25733f8dcd7ce62611 Additional Hang Signature 4: 86a2 Additional Hang Signature 5: 86a291031dfa78c9345eaec1c8ceefb6 Additional Hang Signature 6: 4b95 Additional Hang Signature 7: 4b95ef3a28d29f25733f8dcd7ce62611 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt |
| [2013-11-12 03:42:39] |
| |
|
We do not see how we can help with a problem like this other than refer to help topic 17 here: Http://www.sierrachart.com/index.php?l=doc/helpdetails17.html The problem is not within Sierra Chart. It must be within the custom study. 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 |
| [2013-11-12 12:27:50] |
| hairyMug - Posts: 31 |
|
Thank you but I don't think I have explained it properly. All the custom studies work correctly, the problem only occurs, (and not always), when the study is replaced and an input has been changed. After restarting, the study can be added or replaced with no issue. I am thinking when the study is added, there is some registration routine in SC which attempts to map the current input variables to the new input variables, and since some of the input variable names were changed, it fails to map and then hangs. This only started after version 1035; previous versions never did this. I will attempt to determine the steps to reproduce 100% of the time (if possible). |
| [2013-11-12 17:18:40] |
| |
|
I am thinking when the study is added, there is some registration routine in SC which attempts to map the current input variables to the new input variables, and since some of the input variable names were changed, it fails to map and then hangs. No, this does not happen. There should be no trouble with changing inputs and even keeping the same study on the chart.Are you using the Sierra Chart built-in compiler? If so, we will test this. 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: 2013-11-12 17:19:34
|
| [2013-11-23 18:24:59] |
| hairyMug - Posts: 31 |
|
This problem is now more frequent and has nothing to do with compiling... it occurs after changing the inputs and backtesting multiple times. There are now two crash messages. The first: -------------------------------------------------------------------- Problem signature: Problem Event Name: APPCRASH Application Name: SierraChart.exe Application Version: 700.0.0.0 Application Timestamp: 528ffdfb Fault Module Name: MSVCR100.dll Fault Module Version: 10.0.40219.325 Fault Module Timestamp: 4df2be1e Exception Code: c0000005 Exception Offset: 0001d3d5 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789 --------------------------------------------------------------------- And Then another message: --------------------------------------------------------------------- Problem signature: Problem Event Name: APPCRASH Application Name: SierraChart.exe Application Version: 700.0.0.0 Application Timestamp: 528ffdfb Fault Module Name: ntdll.dll Fault Module Version: 6.1.7601.18229 Fault Module Timestamp: 51fb1072 Exception Code: c015000f Exception Offset: 0008482b OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: e520 Additional Information 2: e5203e0497da4635e246293afbe96216 Additional Information 3: dcd2 Additional Information 4: dcd2c6bc307c58e912c27eed76ef9a8d ------------------------------------------------------------------------------ Note: I am running the latest version (1051) and my system has all SSDs and not disk drives... Hopefully this will give a clue as to where things are failing... >> I will also attempt re-compiling using the SC compiler but I don't have much hope that it will change anything. |
| [2013-11-23 21:39:32] |
| |
|
it occurs after changing the inputs and backtesting multiple times. This can only be coincidental. It could not in and of itself be the cause of the problem.It is entirely possible your custom study is causing a memory corruption and then causing this problem at a later point in time. We do not see how we can help with this problem. If there was something wrong with what happens when Add Custom Study is used, we would have widespread reports of this. While certainly we do periodically have reports of problems with that, It is always because of a faulty DLL file or some bug with it. One suggestion is make sure you have a return statement at the bottom of every sc.SetDefaults code block. 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 |
To post a message in this thread, you need to log in with your Sierra Chart account: