Support Board
Date/Time: Fri, 22 May 2026 02:21:42 +0000
v2896 - not backward compatible, huge memory usage, not responsive
View Count: 219
| [2026-04-06 19:09:57] |
| User719512 - Posts: 436 |
|
Hi Sierra Chart Engineering, v2896 is not backwards compatible with my custom studies and I see a huge memory usage and hang/not responsive status in task manager. v2891 - chart runs fine, memory usage ~700MB v2896 - chart hangs, memory usage 28GB (see image) If I recompile all my studies after fixing the errors from the new headers (Volume to GetVolume() etc) then: v2896 - chart runs fine, memory usage ~700MB So something is not backwards compatible. Expectation was API calls using s_VolumeAtPriceV2 would return "empty". So while I can make my custom studies work for the new builds, it will be a scramble to communicate this to customers and a lot of coordination would be required to have Sierra release v2896+ in current state, tell customers not to use pre-v2896, rebuild and release v2896 custom studies, and then have all customers update and receive matching Sierra and custom studies. Happy to discuss more, help debug, etc. Still looking at things on my side as well and that is taking time. Thanks |
 Screenshot 2026-04-06 115620.png / V - Attached On 2026-04-06 19:08:59 UTC - Size: 7.19 KB - 54 views |
| [2026-04-06 19:38:57] |
| Tony - Posts: 715 |
|
I just upgraded from v2888 to v2896, didn't notice anything wrong, your issue is probably related to some specific functions.
|
| [2026-04-06 19:42:51] |
| User719512 - Posts: 436 |
|
I think the changes to s_VolumeLevelAtPrice are not backward compatible with studies compiled against older headers. s_VolumeAtPriceV2 reordered members in that struct. Unsure if this is causing the issues reported above for backward compatibilty. Yes @Tony, I am indeed using some of the structures undergoing changes for the "double conversion" in the headers. Mainly related to volume at price (VAP) usage in my custom studies. |
| [2026-04-07 10:03:13] |
| Sierra_Chart Engineering - Posts: 23823 |
|
Version 2896 is still a prerelease, and we have not yet finalized the changes. We apologize for not yet putting out a notice of the changes. There is not back compatibility and the intention is to provide, empty Volume at Price arrays, for all of the Volume at Price arrays being given to ACSIL unless the studies that depend on Volume at Price data are recompiled. We are still working on that. Expectation was API calls using s_VolumeAtPriceV2 would return "empty". Yes this will be the case.
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: 2026-04-07 10:07:20
|
| [2026-04-07 19:11:30] |
| Sierra_Chart Engineering - Posts: 23823 |
|
This is now resolved in 2897. You will get an empty Volume at Price container if studies are not recompiled for 2897 or higher, when using this version or higher.
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 |
To post a message in this thread, you need to log in with your Sierra Chart account: