Created attachment 147299 [details] screen shot Currently working with LOOL/NC on the TDF server. The document is a 40 page writer file, mixed text and images, with a large number of tracked changes. LOOL is being used to review, accept or reject, those changes. I've tried using the Manage Changes dialog and working without it (using the change boxes displayed on the right side of the display). Consistently LOOL will become non-responsive after accepting a dozen or so of the changes. Often (though not always) the 'saving' overlay is displayed at the bottom of the screen while this happens. [see attachment] This has been consistent, open the file, accept changes and within a few minutes of working the lack of response - get out, come back in, start over and it hangs again repeating the cycle.
Continuing to work with the file (have cleared changes through first 24 pages) and the issue continues, but is getting quicker about it. At this point I can accept 3 or 4 changes max before the window stops responding. Good news, it appears that at no time did it fail to save the changes made.
OK - I know this is not quite the expected way to use bugzilla - but I should add, after writing the previous comment I went back to work on the document. This time it worked without fail, finished accepting/rejecting all the tracked changes in the final 20 pages of the document without a problem. The application paused a couple of times (never more than 20 seconds) and showed it was saving the document every so often but always right back to being responsive afterwards.
@Drew Jensen, Could you please share the link to the document ?
(In reply to Xisco Faulí from comment #3) > @Drew Jensen, Could you please share the link to the document ? Apparently I can not - thought I had saved a snap shot of it before all the tracked changes were cleared but seems not to be the case. So - I do another one, a little bigger, with a fairly large set of tracked changes still. Could try this again with a couple of folks from the documentation team meeting tomorrow and see if it acts similarly. If so I'll use that, if not I guess close the issue as being unable to duplicate it.
(In reply to Drew Jensen from comment #4) > (In reply to Xisco Faulí from comment #3) > > @Drew Jensen, Could you please share the link to the document ? > > Apparently I can not - thought I had saved a snap shot of it before all the > tracked changes were cleared but seems not to be the case. > > So - I do another one, a little bigger, with a fairly large set of tracked > changes still. Could try this again with a couple of folks from the > documentation team meeting tomorrow and see if it acts similarly. If so I'll > use that, if not I guess close the issue as being unable to duplicate it. Yes, please do so!
Didn't get a chance to test this with another file - but there will be a chance later. For today I am setting this to resolved insufficient data since the original file is not available any longer. If during later sessions this happens again will reopen and copy the file as an attachment at that time.