View Single Post
Old 05-03-2019, 07:48 AM   #711
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,881
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
In S&R I only see high CPU and Power usage numbers when I use the "Pause and make small adjustments' button, they fall back to low levels when I hit the "Back to the Procedure button" and it goes back to searching.

In Dialogue Check I see those high usages throughout the entire process, when its scrolling (down and up) searching for mismatches, when it finds a mismatch, when I'm correcting the mismatches, right through to End of process popup. That would seem to imply its in the -- The procedure comes into a loop and checks if the 'return' button is pressed -- state all the time.

I received a new version of Office 365 this morning - Version 1904 (Build 11601.20144). I have run a couple of smaller documents through DC that gave me problems a few days ago - guess what they ran through successfully. I'll run the large document that was giving me DC problems before that over the weekend.

BR
BetterRed is offline   Reply With Quote