Jump to content
Medved Trader Forums

stock777

Members
  • Posts

    776
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by stock777

  1. this is what the @ES  volume chart looks like a few minutes after a clear and backfill

    pretty sure this is ameritrade sending crap

    all the other futures symbols are stable

     

    Edit : changing the symbol to @NQ and back again to @ES  on the same chart, cleared this noise, so not sure what thats about.    🙄

     

    Timage.png.a906d72b4b50627c0cb9aba9c1e85b92.png

  2. yahoo is already set to low.  

    and since when does yahoo deliver realtime futures data ?  the LAST quote is still streaming  live when this problem shows up .    Yahoo delivers only slow delayed data

    image.png.320dbf04cff111a58e70254ef3021d2b.png

     

    only  the es  is affected by this issue , the other futures symbols are not . 

    think this is  problem with the ameritrade data feed , not mt

    chart totally busted when rollover comes, as backfill is the old contract , and the feed is the new .  nice

     

  3. Not sure what makes you think that .  What other feed ? I only get ES from ameritrade .  Heres what the quotes look like right now

    notice the no change , change last, or name . The price ,lastvolume  , and volume remain unaffected

    these come back  to normal when i reset the feed using the sources screen

    This happ about 6 diff times today

    As I indicated this only seems to happen sporadically, havent seen it in a long time (ive made no changes to the setup) , and I think its related to the rollover, but not sure.

     

    image.png.e1cb6fb2cd56652eda7209bb58c80b7b.png

     

    image.png.26622cd21daf142c4d4c3e68fde6d2a1.png

  4.  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.

     

     

     

  5.  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 .

     

  6.   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. 

     

     

      

     

  7. 4 hours ago, Jerry Medved said:

    there is no way to tell what the thread was just like that. in order to match the thread, we would need to get a "dump" of the running process, which you can do via right click on the process in the task manager and send it to us. and indicate exact thread #

     

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

     

  8.  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

     

    'image.png.0820a7954ffecb14515a36b5b4fe2878.png

×
×
  • Create New...