libreoffice-gtk conflicts with large lo-writer file

[Jurgen Schellaert]

After opening https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1577093/+attachment/4652522/+files/wlst.odt , LibreOffice becomes unresponsive, graying out from a few minutes to a quarter of an hour at a time. During this, the interface has various presentation issues:
- Two overlapping status bars
- Duplicated vertical scrollbars at the right side
- The title bar covering up the menu bar as well as part of the upper toolbar
- The horizontal ruler shifted to the right, causing the "comments" column to appear on the left rather than the right

When the file eventually gets loaded and the interface is restored, the menus turns out to be unusable: the drop-downs are narrow blacks slabs without any entries and without any responsiveness.

Newly created files or existing smaller files are fine.

WORKAROUND: Uninstall packages:
libreoffice-gnome
libreoffice-gtk

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libreoffice-writer 1:5.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun May 1 05:28:07 2016
InstallationDate: Installed on 2016-04-07 (23 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Benoit Tainturier (b-tainturier)]

I've got 3 computers at home (2 desktop and 1 laptop).
This bug clearly affect 2 computers (a desktop and my Asus UX305-FA). Libreoffice is unusable with big files (more than 100 pages). Removing libreoffice-gtk resolve the issue.
My third computer (desktop) is not affected, but Libreoffice is a bit slow with big files.

This bug appeared with Ubuntu 16.04. Everything was fine with Ubuntu 15.10 and earlier.

[Jurgen Schellaert (jurgen-schellaert-j)]

Just an update: all the issues that I reported were fixed some time ago after upgrading libreoffic-gtk (currently using 1:5.1.4-0ubuntu1).

[dino99 (9d9)]

Closing per comment #4 above.

[Benoit Tainturier (b-tainturier)]

I'm using the current version of libreoffice (1:5.1.4-0ubuntu1).
The issue is still present on my computer.

[Roger Franz (rogerfranz)]

Still present, 5.1.4, under Lubuntu 16.04.

The issue is still present. CPU locked at 100% for minutes on end with a two-page document.

[Sebastien Bacher (seb128)]

Could people having the issue add documents which they are using to the bug?

[Benoit Tainturier (b-tainturier)]

Here is a large document affected by the bug.

This file opens in 3 seconds without libreoffice-gtk and in about 2 minutes with libreoffice-gtk.

[dino99 (9d9)]

You can get more details about what is going on:

- install libreoffice-dbg, valgrind
- then to start libreoffice,from a terminal, run:

soffice --valgrind >& valgrind.log

and select the file you want to work with; do some usual job, save the file and close it, then close libreoffice. Finally open the log file to get the details.

some debugging troubles of my own:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1617301

[Benoit Tainturier (b-tainturier)]

Thanks dino99 for your help. Here is my log file.

[Gorka Navarrete (emrys)]

This seems to be a widespread and critical issue.

With both Ubuntu 16.04 and 16.10, with different computers (e.g. Xeon 64GB RAM 1TB SSD). I have problems with the UI freezing in Writer, Impress, etc. when opening a big file (e.g. with a bunch of images, or Mendeley references), or various mid-sized files to the point it becomes unusable.

For example, having a couple relatively big .odp files opened and copying slides between them completely freezes the UI for a couple minutes.

This happens with LO 5.2.2.2, the 5.3 Beta2, 5.0.6...

Getting rid of libreoffice-gtk* helps a bit, but scrolling is still a pain, etc.

[Gorka Navarrete (emrys)]

I created a LO bug report around this issue, or rather, the more general issue: https://bugs.documentfoundation.org/show_bug.cgi?id=104716

[dino99 (9d9)]

@emrys

please change the status of your report as you have provided the requested example file (otherwise that report will be closed soon).

note: my main issue is with Calc (5.2.2, 5.2.3, 5.2.4); as you its a GUI/Gtk issue: scrolling use too much cpu, and closing the calc's file ends with a crash (pointing to libuno_cppuhelpergcc3; checking its properties, its type is "link to unknown" which looks suspect. wonder if yours also as mine.

[Gorka Navarrete (emrys)]

Thanks. I've done that.

In my case, there are (generally) no crashes, just freezes and terribly
slow scrolling, but there may be some common cause for sure, at least to
part of the problem...

Cheers.

G.

On Fri, Dec 16, 2016 at 1:08 PM, dino99 <email address hidden> wrote:

> @emrys
>
> please change the status of your report as you have provided the
> requested example file (otherwise that report will be closed soon).
>
> note: my main issue is with Calc (5.2.2, 5.2.3, 5.2.4); as you its a
> GUI/Gtk issue: scrolling use too much cpu, and closing the calc's file
> ends with a crash (pointing to libuno_cppuhelpergcc3; checking its
> properties, its type is "link to unknown" which looks suspect. wonder if
> yours also as mine.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1577093
>
> Title:
> libreoffice-gtk conflicts with large lo-writer file
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+
> bug/1577093/+subscriptions
>

[penalvch (penalvch)]

Jurgen Schellaert, to clarify:
1) Did this issue happen in Ubuntu versions prior to 16.04?
2) Is this reproducible in a later version of LibreOffice via https://launchpad.net/~libreoffice ?

[Jurgen Schellaert (jurgen-schellaert-j)]

1) No, previous versions were fine.
2) My issue got solved through an August update (comment #4 above) so I have not seen any reason to test other versions since. All I can say is that I did try launchpad at the time I was experiencing the bug - no 5.2.x was available yet - and that did not help at all. I will try a later version as soon as I find the time.

[penalvch (penalvch)]

Jurgen Schellaert, thanks for the clarification. I'll re-close this report as your issue has long been resolved.