LibreOffice Writer freezes for a minute after loading a file

[Mika Sarlin]

After loading a file (400 pages), Writer freezes for more than a minute (see the attached screenshot). The soffice.bin process uses 50-51% of CPU (= 100% on one processor).

When the file finally opens, the page count is first about 800, then it falls to the correct 400 pages.

Changing the memory, java or font anti aliasing settings doesn't help. The only thing that seems to help is removing the libreoffice-gtk package. However, this makes LibreOffice unusable because of the bug 1514249.

I'm using a fresh installation of Ubuntu 16.04 with all the updates. The Libreoffice version is 5.1.2.2.

[Mika Sarlin (msarlin)]

Installing LibreOffice 5.0.5.2 didn't help, the same problem occurs. In Ubuntu 15.10 (on the same computer) the file works fine.

[penalvch (penalvch)]

Mika Sarlin, thank you for reporting this and helping make Ubuntu better.

Could you please attach the file that demonstrates this problem?

[Mika Sarlin (msarlin)]

Here is my file. Note that I changed all the letters to Xs, but that doesn't affect the bug.

[penalvch (penalvch)]

Mika Sarlin, to clarify:
>"Installing LibreOffice 5.0.5.2 didn't help, the same problem occurs. In Ubuntu 15.10 (on the same computer) the file works fine."

So, which version of LibreOffice were you using specifically in 15.10 when the file worked fine?

[Mika Sarlin (msarlin)]

In Ubuntu 15.10. I have LibreOffice 5.0.5.2.

[Mika Sarlin (msarlin)]

I just upgraded to 5.1.2.2. in Ubuntu 15.10 (ppa:libreoffice/libreoffice-5-1), and it works too. So the file opens fine in Ubuntu 15.10 both with 5.0.5.2 and 5.1.2.2.

[Mika Sarlin (msarlin)]

I just noticed that this bug does not occur if I run LibreOffice as sudo.

[Mika Sarlin (msarlin)]

Latest updates seem to have fixed this, I don't have any problems anymore!

[penalvch (penalvch)]

Mika Sarlin, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1574207/comments/9 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.