stock777

??

Not sure if this is ONLY an after hours problem, but on % move alerts, getting triggers on late prints that are well out of the current bid/ask range ( by $$$'s ) , even thought that setting is chosen.

As it is , I've been creating wave or mp3's with whatever voice alerts I want, but it would be a lot simpler to just be able to type a message into the alert that would be spoken by the speech engine Also , would enable variable output such as "New High Today " + [SYMBOL] You get the drift.

I had this issue crop up again. Fixed again by loading from a backup . Seems to be caused by a corrupted save ?? Got an error message that said something about the number of windows not matching the layout on one of the attempted loads of the last used layout. The other tries simply caused those not responding errors in task manager, and an unusable MT The backup layout from a few days ago worked fine. I keep MT open for a few days at a time, without reloading. Not sure if that's a factor here or not. Seems kind of random as the last problem was over two weeks ago.

Forgot to mention, the problem fixes itself on market open ! Strange

I switched to Yahoo historical daily backfill recently as Ameritrade historical is very spotty with a lot of new and even old symbols . Noticed that pre market , the dates are screwy on the last few days. I forget exactly the issue, think there was no YESTERDAY date , and yesterday and todays price action was combined. Sorry for the poor reportage here. Take a look at it pre 9:30 tomorrow and you'll see the issue, or maybe you're already aware of it .

If I understand, someone else had the same issue , and it randomly went away ? No problem since on my end

You may well be right . Updating to the new build just as the problem showed up confused the issue , adding another variable. If it was the AV , then it was triggered by the latest Windows Update cycle, as nothing else was changed here

Well, a very strange mix of things not working, then working, has me stumped as to what the issue is/was Since the problem first occurred late last night, with very little data written to disk, I'm skeptical that the AV was the culprit. It never has been , so unless MSFT did something really odd in the latest April update to change the AV behavior ... I added the MT.exe process exclusion, and think I reloaded what WAS a problematic layout/settings combo, and now its ok. Not getting that CPU spike in the single thread. Removing that exclusion for testing , seems to have no effect at all. So I have no idea what fixed it 🤔 Sorry to say. Hopefully its fixed for good.

I thought that long stack trace i posted above last night would have given enough info to determine what the process parent was ?

Like I said, this problem appeared out of nowhere. Seemed to happen on the update to new build, but I'm running that now with no issue . Did you identify which function the thread info I posted about was related to ? No question that's where the problem was showing up. Just looked at the thread screen again in proc explorer. NOT seeing that 6% cpu usage at all, and thats while now running TWO other high usage apps ! alongside. IB and TOS. Possible theres some weird after hours bug, but I'll check it later. Curious to see if excluding the process made a diff. Like I say, been running MT for YEARS and never had to do that , or for any other program for that matter '

Actually, I never used the process exclusion function , and barely noticed it. Never needed to . Learn something every day. I added it , but notice no change in cpu usage, at least with the current working layout. When I get a chance later I'll test the broken layout again with this new exclusion

ok, simple enough. were you able to run that layout without any issue ?

You talking about mt.exe ? Thought excluding the folder covered everything in it Still dont get why the focus on AV here. I've been using MT since DAY 1, under the exact same conditions, and all of a sudden something extreme showed up . You really think this is AV related ??? Anything possible , but it wouldnt be my first guess

fwiw, these are the current exclusions

I thought I was clear that restoring a previous layout fixed the issue I think that pretty much eliminates outside factors no ? I even disabled the AV scanner just to check for that . If you have the most recent layout from my debug upload, look at it. If not I can resend the zip

Not sure why I didnt hear back from you so went ahead tried restoring the prev working version (only the main program directory) , which did not seem to help. No idea how this went to crap so fast Loaded the BASIC layout, and that of course has no problem with cpu. Restored successively older layouts of mine until one finally seemed relatively stable, and at least I could use the program. Noticed that one very busy thread (posted in the prev message) is still chewing cpu with a big difference, the usage ebbs and flows, where in the bad layouts , the usage is a CONSTANT 6-8%, causing severe unresponsiveness. So theres something in my layout that all of a sudden is not playing nice.

Any luck ? I need to do something to get this working tonight. Rolling back seems the easiest fix until we can figure out the problem (Im assuming that will fix it 🙄)

This is the stack for that process dont think anything should be using 6-8% cpu ntdll.dll!RtlMoveMemory+0x1d3 ntdll.dll!RtlReleaseSRWLockShared+0xeb9 ntdll.dll!RtlReAllocateHeap+0x2a3 ntdll.dll!RtlReAllocateHeap+0x7d gdiplus.dll!GdipCreateBitmapFromScan0+0x15f29 gdiplus.dll!GdipCreateBitmapFromScan0+0x18a55 gdiplus.dll!GdipCreateBitmapFromScan0+0x1781d gdiplus.dll!GdipCreateBitmapFromScan0+0x1674b gdiplus.dll!GdipMultiplyMatrix+0xb03 gdiplus.dll!GdipCreateBitmapFromScan0+0x1b513 gdiplus.dll!GdipMultiplyMatrix+0x8cd gdiplus.dll!GdipCreateBitmapFromScan0+0x19706 gdiplus.dll!GdipCreateBitmapFromScan0+0x109b3 gdiplus.dll!GdipDrawRectangle+0x54d gdiplus.dll!GdipDrawRectangle+0x4a9 gdiplus.dll!GdipSetMatrixElements+0x7d7 gdiplus.dll!GdipDrawLines+0xb2 gdiplus.dll!GdipDrawLinesI+0xa3 [Native Frame: IL Method without Metadata] [Managed to Unmanaged Transition] C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll!System.Drawing.Graphics.DrawLines+0x99 D:\Program Files\Medved Trader\TeeChart.Client.dll!Steema.TeeChart.Drawing.Graphics3DGdiPlus.DrawCurve+0x376 D:\Program Files\Medved Trader\TeeChart.Client.dll!Steema.TeeChart.Styles.FastLine.Draw+0x27b D:\Program Files\Medved Trader\TeeChart.Client.dll!Steema.TeeChart.Styles.Series.DrawSeries+0x935 D:\Program Files\Medved Trader\TeeChart.Client.dll!Steema.TeeChart.Chart.DoDraw+0x390 D:\Program Files\Medved Trader\TeeChart.Client.dll!Steema.TeeChart.Chart.DrawAllSeries+0x197 D:\Program Files\Medved Trader\TeeChart.Client.dll!Steema.TeeChart.Chart.InternalDraw+0x7ce D:\Program Files\Medved Trader\TeeChart.Client.dll!Steema.TeeChart.Chart.InternalDraw+0x31 D:\Program Files\Medved Trader\TeeChart.Client.dll!Steema.TeeChart.TChart.Draw+0xa61 D:\Program Files\Medved Trader\TeeChart.Client.dll!Steema.TeeChart.TChart.OnPaint+0x310 C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!System.Windows.Forms.Control.PaintWithErrorHandling+0x67 C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!System.Windows.Forms.Control.WmPaint+0x3d2 C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!System.Windows.Forms.Control.WndProc+0x320 C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.Callback+0xc2 [Unmanaged to Managed Transition] [Native Frame: IL Method without Metadata] clr.dll+0x222e USER32.dll!CallWindowProcW+0x3f8 USER32.dll!DispatchMessageW+0x39c USER32.dll!SendMessageTimeoutW+0x143 ntdll.dll!KiUserCallbackDispatcher+0x24 win32u.dll!NtUserCallHwndLock+0x14 [Native Frame: IL Method without Metadata] [Managed to Unmanaged Transition] C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!System.Windows.Forms.Control.Update+0x30 D:\Program Files\Medved Trader\MT.exe!MT.ChartInfo.RefreshChart+0x46f D:\Program Files\Medved Trader\MT.exe!MT.ChartWindowCharts.RefreshAll+0xb5 D:\Program Files\Medved Trader\MT.exe!MT.ChartWindow.InvalidateChart+0x6d D:\Program Files\Medved Trader\MT.exe!MT.ChartWindow.RecalcAndPaintAllCharts+0xcba [Unmanaged to Managed Transition] clr.dll!LogHelp_TerminateOnAssert+0x1b93 clr.dll!LogHelp_TerminateOnAssert+0x1aa4 clr.dll!MetaDataGetDispenser+0x32cd2 clr.dll!MetaDataGetDispenser+0x33145 [Managed to Unmanaged Transition] C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll!System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal+0x84 C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll!System.Delegate.DynamicInvokeImpl+0xa0 C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!System.Windows.Forms.Control.InvokeMarshaledCallbackDo+0x9d C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!System.Windows.Forms.Control.InvokeMarshaledCallbackHelper+0x69 C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll!System.Threading.ExecutionContext.RunInternal+0x172 C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll!System.Threading.ExecutionContext.Run+0x15 C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll!System.Threading.ExecutionContext.Run+0x55 C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!System.Windows.Forms.Control.InvokeMarshaledCallback+0xbc C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!System.Windows.Forms.Control.InvokeMarshaledCallbacks+0xe6 C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!System.Windows.Forms.Control.WndProc+0x509 C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.Callback+0xc2 [Unmanaged to Managed Transition] [Native Frame: IL Method without Metadata] clr.dll+0x222e USER32.dll!CallWindowProcW+0x3f8 USER32.dll!DispatchMessageW+0x259 [Native Frame: IL Method without Metadata] [Managed to Unmanaged Transition] C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop+0x341 C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!ThreadContext.RunMessageLoopInner+0x1c7 C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll!ThreadContext.RunMessageLoop+0x52 D:\Program Files\Medved Trader\MT.exe!<>c__DisplayClass78_0.<CreateInThread>b__0+0x306 C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll!System.Threading.ExecutionContext.RunInternal+0x172 C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll!System.Threading.ExecutionContext.Run+0x15 C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll!System.Threading.ExecutionContext.Run+0x55 C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll!System.Threading.ThreadHelper.ThreadStart+0x55 [Unmanaged to Managed Transition] clr.dll!LogHelp_TerminateOnAssert+0x1b93 clr.dll!LogHelp_TerminateOnAssert+0x1aa4 clr.dll!LogHelp_TerminateOnAssert+0x2358 clr.dll!MetaDataGetDispenser+0x12a2f clr.dll!LogHelp_TerminateOnAssert+0x2f50 clr.dll!LogHelp_TerminateOnAssert+0x2ec3 clr.dll!LogHelp_TerminateOnAssert+0x2e02 clr.dll!LogHelp_TerminateOnAssert+0x2fe7 clr.dll!MetaDataGetDispenser+0x12919 clr.dll!LogHelp_TerminateOnAssert+0x6835 KERNEL32.dll!BaseThreadInitThunk+0x14 ntdll.dll!RtlUserThreadStart+0x21

PS , if i restore from a backup, what dirs do i need to use . Is it just the main program DIR, or some of the others? Over my pay grade, but was browsing process explorer for clues as to where the hang is. This looks suspicious, top line

PS , if i restore from a backup, what dirs do i need to use . Is it just the main program DIR, or some of the others?

Keep in mind Ive made no changes other than this months Windows Update over the weekend. And MT seemed to run well enough today, before updating to the new prod version . I use the built in Microsoft Defender, and nothing else. I added any dirs to the exclusions that werent there, and no diff in the problem. Whats the easiest way for me to rollback to the previous beta . I can restore from a recent drive backup but if theres a more direct way, lets try that

First time in a long while I've seen problems like this. I thought I noticed something tonight even on the latest beta before updating , but used it all day today and no issues. Loaded up the new prod build and not usable. High CPU, not responding errors on various windows in task manager, very slow response to any menu request or clicking on a chart. Takes up to a minute for the settings menu to come up. seems like theres some process running in hard loop Tried all the easy stuff. 1) deleted the sdata.bin and snews database 2) loaded a backup of settings from last week 3) rebooted pc No luck with any of those . I sent the log along as well.

Notice we're not getting a backfill on the trading from 4am to 7am EST , using Ameritrade . The TOS platform has this data.

I mention not fixing things as they still have probably dozens if not over a hundred symbols that do not historical backfill correctly. I run into them all the time and have to use Yahoo Not practical to forward a list, they need to do this properly at their end . Is this rocket science ?