Home >> Support Board

Support Board

Date/Time: Fri, 26 Apr 2024 17:41:48 +0000

How to Post a Message for Support

Heap Corruption

View Count: 4353

[2013-11-25 20:01:41] #1 [Go To First Post]
bfalk - Posts: 33
There seems to be some form of heap corruption, hard to say where without SC symbols. I produced this bug by opening up 8 chartbooks with DOMs and intraday charts with no data behind them (all the data has to be fetched). Reproduces. I have a full memory dump if the bug isn't obvious enough from the stack trace (which it probably isn't, yay heap corruption bugs). APPLICATION_VERIFIER_HEAPS_CORRUPTED_HEAP_BLOCK_START_STAMP (10) Corrupted start stamp for heap block. This happens for buffer underruns. Arguments: Arg1: 07c71000, Heap handle used in the call. Arg2: 255e0ec0, Heap block involved in the operation. Arg3: 00064140, Size of the heap block. Arg4: abcdbbbb, Corrupted stamp value. FAULTING_IP: verifier!VerifierStopMessage+1f8 6abbba58 cc int 3 EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 6abbba58 (verifier!VerifierStopMessage+0x000001f8) ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 1 Parameter[0]: 00000000 CONTEXT: 00000000 -- (.cxr 0x0;r) eax=00000000 ebx=00000000 ecx=6abe8598 edx=00000000 esi=07c70000 edi=07c70000 eip=6abbba58 esp=0018edb8 ebp=0018edd4 iopl=0 nv up ei pl zr na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000244 verifier!VerifierStopMessage+0x1f8: 6abbba58 cc int 3 DEFAULT_BUCKET_ID: WRONG_SYMBOLS PROCESS_NAME: SierraChart.exe ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached. EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid EXCEPTION_PARAMETER1: 00000000 NTGLOBALFLAG: 2000000 APPLICATION_VERIFIER_FLAGS: 0 APP: sierrachart.exe ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) x86fre MANAGED_STACK: (TransitionMU) 0018F4AC 08879396 SierraChart!DomainBoundILStubClass.IL_STUB_PInvoke()+0x56 (TransitionUM) MANAGED_STACK_COMMAND: _EFN_StackTrace PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS LAST_CONTROL_TRANSFER: from 6abb9e69 to 6abbba58 STACK_TEXT: 0018edd4 6abb9e69 00000010 6abb15dc 07c71000 verifier!VerifierStopMessage+0x1f8 0018ee38 6abba22a 07c71000 00000004 255e0ec0 verifier!AVrfpDphReportCorruptedBlock+0x239 0018ee94 6abba742 07c71000 255e0ec0 00000004 verifier!AVrfpDphCheckNormalHeapBlock+0x11a 0018eeb4 6abb90d3 07c71000 00230000 01001002 verifier!AVrfpDphNormalHeapFree+0x22 0018eed8 77561464 07c70000 01001002 255e0ec0 verifier!AVrfDebugPageHeapFree+0xe3 0018ef20 7751ab3a 07c70000 01001002 255e0ec0 ntdll!RtlDebugFreeHeap+0x2f 0018f014 774c3472 00000000 255e0ec0 13a188d0 ntdll!RtlpFreeHeap+0x5d 0018f034 755614dd 07c70000 00000000 255e0ec0 ntdll!RtlFreeHeap+0x142 0018f048 72f5016a 07c70000 00000000 255e0ec0 kernel32!HeapFree+0x14 0018f05c 005a8749 255e0ec0 00000000 00170eee msvcr100!free+0x1c WARNING: Stack unwind information not available. Following frames may be wrong. 0018f138 760162fa 00170eee 0000801b 00000000 SierraChart+0x1a8749 0018f164 76016d3a 00409ad0 00170eee 0000801b user32!InternalCallWinProc+0x23 0018f1dc 76020d27 00000000 00409ad0 00170eee user32!UserCallWinProcCheckWow+0x109 0018f214 7602794a 00409ad0 00170eee 0000801b user32!CallWindowProcAorW+0xab 0018f234 65b2da57 00409ad0 00170eee 0000801b user32!CallWindowProcA+0x1b 0018f2b8 760162fa 00170eee 0000801b 00000000 mfc100!_AfxActivationWndProc+0x139 0018f2e4 76016d3a 65b2d91e 00170eee 0000801b user32!InternalCallWinProc+0x23 0018f35c 760177c4 00000000 65b2d91e 00170eee user32!UserCallWinProcCheckWow+0x109 0018f3bc 76017bca 65b2d91e 00000001 0018f3fc user32!DispatchMessageWorker+0x3bc 0018f3cc 65b1bdf4 07bd5f28 00000000 009e5e38 user32!DispatchMessageA+0xf 0018f3dc 65b1c47c 009e5e38 009e5e38 ffffffff mfc100!AfxInternalPumpMessage+0x40 0018f3fc 65b41c4c 009ecd60 0032cffe 00000000 mfc100!CWinThread::Run+0x5b 0018f410 0075b36f 00400000 00000000 0032cffe mfc100!AfxWinMain+0x6a 0018f4d8 65252652 08c6ead0 0018f538 6526264f SierraChart+0x35b36f 0018f4e4 6526264f 0018f584 0018f528 65374d4e clr!CallDescrWorkerInternal+0x34 0018f538 65262e95 0018f680 00000001 00000000 clr!CallDescrWorkerWithHandler+0x6b 0018f5b8 653ea887 0018f6b4 57de377f 057134dc clr!MethodDescCallSite::CallTargetWorker+0x152 0018f6e4 65317610 00000000 00000001 57de3763 clr!RunMain+0x196 0018f958 653a1dc4 00000000 57de38f3 00400000 clr!Assembly::ExecuteMainMethod+0x124 0018fe5c 653a1e67 57de3f23 00000000 00000000 clr!SystemDomain::ExecuteMainMethod+0x614 0018feb8 653a1f7a 57de3f63 00000000 00000000 clr!ExecuteEXE+0x4c 0018fef8 653a416a 57de3eaf 00000000 00000000 clr!_CorExeMainInternal+0xdc 0018ff34 6701f5a3 57dd746e 00000000 75561222 clr!_CorExeMain+0x4d 0018ff70 6ac47f16 00000000 67010000 0018ff94 mscoreei!_CorExeMain+0x10a 0018ff80 6ac44de3 00000000 755633ca fffde000 mscoree!ShellShim__CorExeMain+0x99 0018ff88 755633ca fffde000 0018ffd4 774c9ed2 mscoree!_CorExeMain_Exported+0x8 0018ff94 774c9ed2 fffde000 493cca52 00000000 kernel32!BaseThreadInitThunk+0xe 0018ffd4 774c9ea5 6ac44ddb fffde000 00000000 ntdll!__RtlUserThreadStart+0x70 0018ffec 00000000 6ac44ddb fffde000 00000000 ntdll!_RtlUserThreadStart+0x1b STACK_COMMAND: ~0s; .ecxr ; kb FOLLOWUP_IP: SierraChart+1a8749 005a8749 83c404 add esp,4 SYMBOL_STACK_INDEX: a SYMBOL_NAME: sierrachart+1a8749 FOLLOWUP_NAME: MachineOwner MODULE_NAME: SierraChart IMAGE_NAME: SierraChart.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5292ca63 FAILURE_BUCKET_ID: WRONG_SYMBOLS_80000003_SierraChart.exe!Unknown BUCKET_ID: APPLICATION_FAULT_WRONG_SYMBOLS_sierrachart+1a8749 ANALYSIS_SOURCE: UM FAILURE_ID_HASH_STRING: um:wrong_symbols_80000003_sierrachart.exe!unknown FAILURE_ID_HASH: {b81c6cf6-12ca-fe14-7272-6dc5fbf1685f} Followup: MachineOwner ---------

[2013-11-29 21:51:19] #2 [Go To First Post]
bfalk - Posts: 33
Any chance you have had time to look at this. It has only been around since 1049 when the historical improvements came around. Perhaps it's a cross-thread sharing issue of variables? 1048.0 prerelease does not have this issue. I'd love to look into it, but I'm not going to waste too much time without symbols. -B

[2013-11-30 00:05:00] #3 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
When we first saw this we did not have enough information to be able to reproduce the problem. This last message gave us and indication of what is causing it and we are solving it now. 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-30 01:10:02] #4 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We are putting out version 1055 in about 10 minutes. Let us know if it resolves the problem. This has all of the latest performance improvements. So there should be overall improved performance with data downloading and real-time updating. 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-30 07:04:34] #5 [Go To First Post]
bfalk - Posts: 33
All good with 1055. Thanks!

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