Created attachment 153642 [details] Complex file that causes the bug When I open a complex CALC file (with a lot of sheets and macros in it) the whole opened LO applications can't be scrolled using mouse wheel. In my case I had opened 3 applications: CALC (4 files opened, including the complex one) WRITE (1 file opened) BASIC IDE Another thing that happens is that cell cursor is no more visible and cells selected range is not highlighted. When the file is closed, everything goes back to normal. My LO release is 6.3.0.4, running on Ubuntu 18.04, Build ID: 1:6.3.0-0ubuntu0.18.04.1~lo2 I attach the file that gives me the problem (with previous LO version there were no problems opening this file). Although complex, this file is relatively small (125,3 kB).
Also here the same problem with calc sheets with checkboxes, choice boxes and so on.
Created attachment 154247 [details] localc sheet
In Addition to my previous comment I notized that LoCalc creates a hight CPU load with such a file but only in the working mode. If I change in the draft mode (extras->forms->draft mode) all seems o.k. It is a problem with LO version 6.3.1 because with version 6.1 all works fine. I attached a file which create such problems.
I have the same problem with Libreoffice 6.3.3.2 in Xubuntu 18.04 When I open a complex Calc sheet the mouse scrolling does not work and I see a high CPU usage. The 99% of the Calc files I work on have many macros, buttons, editboxes, etc, so for me the scrolling does not work in any of my files. Everything works fine in Libreoffice 6.2.8.2.
I just tested with Libreoffice 6.4.0.0.alpha1 and the problem is there too, scrolling does not work in complex files.
I believe this is a duplicate of bug 121963. Could you please try to reproduce it with the latest version of LibreOffice ( 6.3.4.2 ) from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version
I've tested the new version and all, now, works as expected. So the bug, for me, is solved. I mark it as solved (don't know if it is my task, but I did it). Thank you.
Thanks for retesting with the latest version. Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.