Support Board
Date/Time: Mon, 10 Mar 2025 03:11:23 +0000
Unusual behavior after downgrading from v2368
View Count: 546
| [2022-03-16 04:26:59] |
| jwick - Posts: 142 |
|
Hi ... I upgraded from v2308 to v2368. The latter was causing unusual behavior with my code (have made another post detailing this). So I downgraded back to v2308. However, upon downgrading, loading the same chartbooks I loaded previously (and in safe mode), SC is using over 110 GB of memory! I understand SC can't control OS file cachine but I'm not sure this is it. In the past SC has used at most 20 GB of memory and that's with pretty complex studies loaded. Would v2368 have altered my scid files because of the new back adjustments method? Would the downgrade process have not gone smoothly and corrupted something? How can I safely get my environment back to how it was in v2308? I'm very concerned with updating SC at this moment. I do notice some unusual entries in my message log (attached). |
 mem_use.png / V - Attached On 2022-03-16 04:24:46 UTC - Size: 33.95 KB - 147 views  msglog.txt - Attached On 2022-03-16 04:26:50 UTC - Size: 91.27 KB - 229 views |
| [2022-03-16 04:53:31] |
| jwick - Posts: 142 |
|
I've verified that v2368 appears to change the format in .cht chartbook files such that after a downgrade it results in this unusual burst in RAM usage / possibly other unexpected results. Using a backup of the chartbook, everything loaded as expected. I've attached both versions of the chartbook in case it's of any use.
|
Private File Private File |
| [2022-03-16 13:03:04] |
| |
|
The two settings to check that would have a significant impact on memory are the following: Chart Settings: Tick Size (Chart >> Chart Settings >> Symbol >> Symbol Settings menu) Chart Settings: Days-Minutes-Seconds-Milliseconds Per Bar (Chart >> Chart Settings >> Bar Period >> Intraday Chart Bar Period Settings menu) I've verified that v2368 appears to change the format in .cht chartbook files No, the format is not different. Check the above settings, in the Chartbook that you saved after updating to the new version and then rolling back. See if they have changed.There must be some difference in Chart Settings but we do not know what it is. We had a quick look at your Chartbooks looking at one of the charts and those particular settings. We did not notice a difference. And there are too many charts to go through. 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: 2022-03-16 13:11:13
|
| [2022-03-16 13:22:09] |
| jwick - Posts: 142 |
|
There are many charts in the chartbook, but looking at one of them I believe those settings are the same. In the message logs posted earlier, there are several lines like the ones below (line 121) ... is that relevant? Chart (YM-202203-ECBOT) | Encountered unknown Chartbook Field. Field Code: 600. Previous Field Code: 128 | 2022-03-16 00:18:17.540 Chart (YM-202203-ECBOT) | Encountered unknown Chartbook Field. Field Code: 601. Previous Field Code: 558 | 2022-03-16 00:18:17.542 Chart (YM-202203-ECBOT) | Encountered unknown Chartbook Field. Field Code: 602. Previous Field Code: 601 | 2022-03-16 00:18:17.542 Chart (YM-202203-ECBOT) | Encountered unknown Chartbook Field. Field Code: 603. Previous Field Code: 602 | 2022-03-16 00:18:17.542 Chart (YM-202203-ECBOT) | Encountered unknown Chartbook Field. Field Code: 605. Previous Field Code: 594 | 2022-03-16 00:18:17.542 Chart (YM-202203-ECBOT) | Encountered unknown Chartbook Field. Field Code: 606. Previous Field Code: 605 | 2022-03-16 00:18:17.542 Chart (YM-202203-ECBOT) | Encountered unknown Chartbook Field. Field Code: 607. Previous Field Code: 606 | 2022-03-16 00:18:17.542 Date Time Of Last Edit: 2022-03-16 13:22:46
|
| [2022-03-16 13:40:09] |
| |
|
No, this definitely has no relevancy. This just means the newer versions of Sierra Chart have fields which are not supported in older version. These are just not relevant at all.
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: 2022-03-16 13:40:20
|
To post a message in this thread, you need to log in with your Sierra Chart account: