Writer uses 100% cpu for documents created from a particular template

I have a Writer document template that I use for reports.

Running with (and various previous versions) under macOS (El Capitan and High Sierra) is ok for a while (minutes), but after a while the CPU goes to 100%, even when Writer is not being used (including when it is in the background).

I only see this with documents created using this template.

Any ideas what within the template could be causing this?

I can recreate the template, but it is complex with a lot of styles, so I would rather only have to do this as a last resort.

LibreOffice can be really slow and go high CPU when embedding fonts.
I kept having documents which were grindingly slow until I realized the template had embedded fonts.
Turned-off embedded fonts in the documents.
Turned-off embedded fonts in the template.
The delay opening or saving was much reduced.

You may also be seeing this when auto-save is saving the document.

If you must have embedded fonts, do it as a last step.


Thanks for the pointer, but I’m sure that’s not the issue I’m seeing. General performance is not an issue, even when this problem shows. Something is just spinning in a loop, the only real consequence being that my laptop battery runs down very quickly!

I have upgraded to in the past few days and have not seen the issue since, so it’s possible that the cause has been fixed. I’ll keep an eye on things and see how it goes.

Hi - Apart from several styles what else can you tell us about the Template? This might help with either its the template or something else? :slight_smile:
if you find a fix yourself please also post here to help others. Thanks.

Good question. I don’t think there’s anything special about it - character, paragraph and page styles, Open Sans as an embedded font and a custom colour setting. It does have some fairly complex (but small) table structures that are used to position content within headers/footers.

I have also used files created with this template under Windows and not noticed the same issue.