• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
is Time Travel Debug (TTD) useful for debugging this problem?
#2
Hello Rod,

The previous file that was shared with me was useful in the sense that I could attach a debugger and see what code was being executed during the long delay. The unfortunate result is that none of my code was actively being run - the code that was executing was all in the Microsoft framework, so I have no idea what it was doing. If you capture a TTD file, I'll be happy to check it out to see if the result is the same. 

The main problem is that, even with testing on four separate windows 10 machines, I've only ever seen small pauses during UI updates. I've definitely never seen extended 10+ delays like you are describing. So without being able to actively reproduce the problem, I really don't know what to look for. I could set up extensive logging to try and measure the time each section of code is taking, but this will only really work if we have an idea about what code to isolate the timing tests to, as there is far too much code otherwise. If you have an idea about what actions cause the delay and you want to test out some custom builds, I'll be happy to work with you on that. I'll just have to send them to you over email.

Thanks,
Mike
Reply


Messages In This Thread
RE: is Time Travel Debug (TTD) useful for debugging this problem? - by Zubersoft - 07-31-2019, 02:39 PM

Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2019 MyBB Group.