Home >> Support Board

Support Board

Date/Time: Mon, 06 Apr 2026 22:37:42 +0000

How to Post a Message for Support

v2896 - not backward compatible, huge memory usage, not responsive

View Count: 28

[2026-04-06 19:09:57] #1 [Go To First Post]
User719512 - Posts: 431
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 - 6 views

[2026-04-06 19:38:57] #2 [Go To First Post]
Tony - Posts: 714
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] #3 [Go To First Post]
User719512 - Posts: 431
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.

To post a message in this thread, you need to log in with your Sierra Chart account: