Bug 120561 - LibreOffice Writer drains battery by 100% cpu load
Summary: LibreOffice Writer drains battery by 100% cpu load
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.6.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-13 11:35 UTC by nicolas.hueppelshaeuser
Modified: 2018-11-11 09:27 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nicolas.hueppelshaeuser 2018-10-13 11:35:10 UTC
Description:
Working on a document for a couple of weeks now, from some point on I realised that writer kicks the cpu load to 100% right after opening the document and me doing nothing at all (no typing, no re-arranging).  There is a single extension in use: Zotero LibreOffice Integration 5.0.14, but even if disabled, the cpu load remains at 100% just after opening the document.

The document itself consists of 25 pages with four frames, each holding a table, which I'd rate as nothing fancy nor complicated. Not even the 'track changes' feature is activated. There are references to the tables.

The impact is a dramatically decreased battery life time of the system and significant heat production.

After playing with the UserProfile Settings the problem seems to be triggered by having Umlauts in the name field of the user data. If I drop the Umlauts, close Writer and double click my document again, libreoffice writer starts up and maintains a reasonable cpu load.  If I reintroduce Umlauts into the name field, exit libreoffice and open the document again, the 100% cpu load is back.

Steps to Reproduce:
See description. Not reproducible with an empty document.

Actual Results:
CPU load consumed by writer is constantly 100%.

Expected Results:
Reasonable cpu load.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
LibreOffice Writer
Version: 6.0.6.2
Build ID: 1:6.0.6-0ubuntu0.18.04.1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: de-DE (de_DE.UTF-8); Calc: group

OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5300 (Broadwell GT2)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.5
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.0.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:
Comment 1 Jean-Baptiste Faure 2018-10-14 14:35:00 UTC
Make summary more precise.

Best regards. JBF
Comment 2 nicolas.hueppelshaeuser 2018-10-14 15:17:32 UTC
It is not that easy.

In order to get captions in the correct document language I had to switch the language of the user interface from German to English.  After doing so, the 100% cpu load is back — despite of not having any umlauts in the user data.  So the latter turned out be a wild (if educated) guess.  Sorry.
Comment 3 nicolas.hueppelshaeuser 2018-10-14 15:19:08 UTC
Update summary.
Comment 4 nicolas.hueppelshaeuser 2018-10-20 07:06:55 UTC
After monitoring the problem and possible relation to user settings: I think that's a red herring.  I can't see any relation of the kind "with this configuration/settings the problem is triggered, with another configuration it is not".  Changing settings/configuration might yield a temporary change in cpu consumption.  But essentially libreoffice burns up 100% of cpu time when this document is opened.

=> Will change back the ticket summary to the original version.
Comment 5 nicolas.hueppelshaeuser 2018-11-01 11:11:54 UTC
I'm still working on the same document, and still the cpu load sticks to 100%.

By accident I might have found a clue to what is going on. If I open the navigator on the side of the screen, a flickering of the scroll bars indicate a constant rebuild and re-draw of the document contents. The "flicker frequency" is about one second.
Comment 6 nicolas.hueppelshaeuser 2018-11-11 09:27:59 UTC
The problem has vanished.

There have been no updates to Libre Office or the Zotero and Zotero plugin.
Still there have been updates to my Ubuntu 18.04 system, so I postulate that the problem is attributed to a library used by Libre Office.

Therefore I close this ticket as 'resolved'.