Bug 129607 - 25% use of CPU if working with very large writer.exe files after Recovery Mode
Summary: 25% use of CPU if working with very large writer.exe files after Recovery Mode
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.3.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-25 07:19 UTC by urhen
Modified: 2020-08-21 03:43 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 urhen 2019-12-25 07:19:35 UTC
Description:
Working with 5+ documents and 200 page average, with different font colors and highlights... makes Libreoffice use 25% of CPU for hours if not terminated. Sometimes reproducible by just opening them on system, but a constant issue if documents are opened through Recovery Mode.

A weird workaround is to kill tasks at random, until it magically drops to 0% even if closing same writer tasks stabilizes the CPU consumption or not, depending on how lucky you are. Also happens to Calc.exe, but also with writer.exe without any calc.exe opened or vice-versa.

This is a bug, because I can work around and maintain all files opened at 0% cpu.
Already tried disabling OpenGl, hardware acceleration, installing new versions of Libreoffice (for years).
Either closing 1000pages processes, it might only drop to 0% when closing a random 100 page document. Changing the specific large documents have the same output.

Steps to Reproduce:
1. open very large files at the same time (occurs more frequently by Recovery Mode)
2. CPU 25%
3. All files work normally, not a single renderisation or any visible CPU demanding feature, which a simple text editor wouldn't solve in 5 seconds

Actual Results:
CPU works at 25%, doesn't stop until I start randomly killing Writer tasks in the windows taskbar.

Expected Results:
Rendering very large files to a point where I can manage to work with them without abusing my hardware or depending on me playing with the software at every startup before getting to work. After years with LO.

This is possibly fixable because, I have to work everytime I reopen files until they stop consuming CPU. So, I fix this a lot, just don't know why.
By ending tasks, and reopenning them again, I can finally arrive at my initial intention of editing simple text files with annotation features which LO offers and notepad.exe doesn't.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 6.3.3.2 (x64)
CPU threads: 4; OS: Windows 6.1; UI render: GL; VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: CL
Comment 1 Xisco Faulí 2020-01-21 12:04:40 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 2 QA Administrators 2020-07-21 03:47:35 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2020-08-21 03:43:20 UTC
Dear urhen,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp