Created attachment 170343 [details] This doc lags in version 7 when moving cursor, scrolling or typeing I have a 30 to 40 page document with a Title page, page numbers and a header. I was working in version 6, and recently upgraded to 7.04. Immediately noticed significant cursor lag when trying to move UP or Down in the document as well as trying to scroll. Typing words was also laggy. I thought it was an "early bug" so I waited. I recently upgraded to 7.1.1 and problem is still there. I tried shortening the document ot just a few pages. Still doesn't fix the problem. If I Uninstall v7.xx, and install v6.4.7.2, the problem is fixed. Attached please find a document example that duplicates this problem for me.
Help -> Open in safe mode -> Reset the user profile. Apply And restart
Reviewing the suggestion to open safe mode, I first uninstalled 6.x and reinstalled 7.1.1.2 Unfortunately, the act of re-installing seemed to fix the problem. Since I have had the problem for multiple different installs, and uninstalls, I am at a loss to explain why this last uninstall and reinstall removed the problem. So, I can't test to see if the safe mode method works or not. Clearly there is something causing the issue. But, I am happy that I did not have to erase my user profile.
But report must contain lo version and Help-About system info. If I read this well, problem is gone. Likely a duplicate of https://bugs.documentfoundation.org/show_bug.cgi?id=138068
I respect your Workaround. But the only reason it works is because it "works around" the actual bug. It doesn't actually fix the causative issue. Now, if you can say that after v7, this bug is fixed, that is fine. But if v7 suffers transmitting this bug to v8 etc... then the only fix will always be "safemode", clear your profile. And MOST people don't actually visit bugzilla and have no idea why there Libreoffice is slow. I suspect you guys might know why this bug exists.
Macktek, who do you reproach to and who is "you". Telesto and I are volunteers, Lo is volunteer driven project. I'm Lo user and I give back by QA work, and you. Just consider to be "we" in any way, Qa, Dev, Documentation, donation... Here I pointed you to the possible bug. Rule of thumb is search before submitting. That bug is a regression, happens all the time, and users report and Qa tests and volunteer fixes, if there's one. Will happen again. See Release notes for all the issues.
As I said, I respect the work-around, and I am merely letting the person who closed this as "resolved" know that I personally would not consider this as closed unless the bug was "fixed" in future versions. If it is, great, if not, then I don't consider a "reset" of a profile as a reasonable bug fix. That's just my humble opinion, from a volunteer user. We all know everyone is doing a good job. Its up to the people here whether they think a workaround is a bug fix or not.
Looking at Bug 138068, the behavior in my report is very similar. There were comments that the bug for windows had been resolved, but I don't think this is the case. I can say that going back to version 6.4.7,2 completely resolved the issue. And returning to 7.1.1 after that seemed to resolve it "temporarily", but then it returned so I tried the profile clear and that did help. However, that is a pretty drastic step to ask the average end-user to perform, which is why I suggest that it should not be considered closed unless there is confidence that the bug is gone in future versions.