Support Board
Date/Time: Sun, 23 Aug 2026 17:28:56 +0000
GetACSDrawingByLineNumber stack corruption v2941/2942
View Count: 45
| [2026-08-23 11:20:11] |
| User907968 - Posts: 882 |
|
GetACSDrawingByLineNumber() appears to write beyond the end of an older s_UseTool structure when running under Sierra Chart v2941/2942. The study DLL was compiled against an earlier Sierra Chart header, v2911. Observations: - v2940, the call does not appear write beyond the end of the older s_UseTool. - v2941, one byte at offset 0x402 is modified, i.e. the third byte beyond the end of the older 0x400-byte structure. - The overwritten byte appears to correspond to the new 8-bit 'ShowMiddlePointPrice' field added to s_UseTool in v2941. - Visual Studio detects this as stack corruption because the write modifies the 0xCC debug guard/fill bytes following the stack-allocated s_UseTool. - Testing a Release build of the same study results in immediate process termination when this code path is executed. |
| [2026-08-23 16:41:47] |
| User719512 - Posts: 465 |
|
I also see this on an existing study compiled for v2911. Sierra just crashes and closes. This will break a lot of studies and cause a lot of support requests if not patched quickly. tl;dr I see this from a debug build of my v2911 study. Run-Time Check Failure #2 - Stack around the variable 'Tool' was corrupted. triggered by: call _RTC_CheckStackVars (07FFE6EEAD9C8h) |
To post a message in this thread, you need to log in with your Sierra Chart account: