stock777
-
Posts
776 -
Joined
-
Last visited
-
Days Won
4
Content Type
Profiles
Forums
Blogs
Gallery
Downloads
Events
Posts posted by stock777
-
-
looking at it during trading hours, the thread usage is more evenly distributed.
Ill check again tonight and try to capture the high single thread usage info / log
-
pretty typical , avg is around 15% now , much higher than the other platforms .
only reason I notice is not performance, but it spikes the temps on the cpu from time time
-
still getting excessive usage, much higher now during market hours
-
There is one thread that uses quite a bit of cpu , even though nothing is going on at 2am. Turning off quotes and alert system doesnt seem to matter.
I dont have debugging tools installed so the name is meaningless, but this is the call stack of the TID in question.
Running latest beta as of 8/31
Does this look normal ?
gdiplus.dll!GdipSaveImageToFile+0x690
gdiplus.dll!GdipGetImageHeight+0x23a1
gdiplus.dll!GdipCreateBitmapFromScan0+0x19400
gdiplus.dll!GdipCreateBitmapFromScan0+0x176ce
gdiplus.dll!GdipCreateBitmapFromScan0+0x168cb
gdiplus.dll!GdipMultiplyMatrix+0xae7
gdiplus.dll!GdipCreateBitmapFromScan0+0x1b7a3
gdiplus.dll!GdipMultiplyMatrix+0x8b1
gdiplus.dll!GdipCreateBitmapFromScan0+0x19996
gdiplus.dll!GdipCreateBitmapFromScan0+0x10a53
gdiplus.dll!GdipDrawRectangle+0x54d
gdiplus.dll!GdipDrawRectangle+0x4a9
gdiplus.dll!GdipSetMatrixElements+0x897
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+0x275
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+0xce5
[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__DisplayClass86_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 -
All symbols entered in the alert editor get quotes automatically, that proves nothing
-
Nope , still get an "F" for Ford alert under TRADE SIZE . Cant see where the symbol is active at all.
-
Might have dealt with this before, but why is it not possible to turn off the FILTER function in Tile view ?
I have a scan that creates alerts, but it prevents looking at the portfolio in Tile View
-
-
Think it disappeared on its own.
I looked everywhere.
-
sorry, I don't see any filtering option on the ALL NEWS feed, which is what I was referring to
-
Any idea how to find where this is coming from ?
Could it be stuck 'internally' in an alert cue ?
-
Its a shame, because its not than much of a difference in terms of data flow , and this cripples the usefulness of the feed
-
Thanks!
-
I dont think this ever happened.
Could really use a filter in the main news feed for excluding garbage.
Same method as the ALERTS box would prob work well .
Those clowns at Benzinga are polluting the feed with endless "Understanding XYZ Unusual Options Activity" headlines.
-
I like to put stock related bitcoin symbols on the same port as #btc.usd
port is set to coinbase but the stock symbols seem to populate fine
not sure exactly how you're doing that , but keep getting the symbol warning popup saying the symbol format for those stocks is wrong.
can we suppress that somehow ?
-
noticed this . delete symbol from active port, but it still triggers alerts . probably until next restart.
some internal list no doubt not updating with delete
-
No ? No opinion on this ?
-
-
-
Having to actually subscribe to a symbol is a horrible way to provide the news feed. I assume this is ameritrade's issue
Im getting a fraction of the full feed through MT and many symbols dont seem to come through at all, probably because of the limit
Any way to handle this better ?
-
Consistently getting hits on volume much lower than 15,000 for the last minute. Please check
-
kind of random at this point, seems to come up when calling up the alerts editor. not every time .
at the moment right click on @es ,add alert , causes the thrown error . same exact error , same line numbers
ill upload the log
-
just getting back to this.
thing is, it only happens rarely, and seems to coincide with the ES contract rollover, and prime symptom is the dropout of the @ES data as pictured above . My guess, its and Ameritrade issue
since last week, the problem has not reoccurred.
-
Got this a few times today when accessing the Alerts editor (when bringing it up , before doing anything with it )
Running latest beta
CPU usage seems high for 2AM
in Support
Posted
I sent the log yesterday