Bug 121091 - After opening LibreOffice 6, it hogs one of my i5 Processors
Summary: After opening LibreOffice 6, it hogs one of my i5 Processors
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.1.2.1 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-01 10:33 UTC by Kobus
Modified: 2019-12-14 03:41 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Resource screen shot (124.59 KB, image/png)
2018-11-01 10:35 UTC, Kobus
Details
Process screen shot (177.21 KB, image/png)
2018-11-01 10:36 UTC, Kobus
Details
My Hardware (10.41 KB, image/png)
2018-11-01 10:37 UTC, Kobus
Details
New Process Screenshot (127.75 KB, image/png)
2018-11-12 16:43 UTC, Kobus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kobus 2018-11-01 10:33:48 UTC
Description:
I have heard my processor fan running at high speed after installing LibreOffice 6.
I found that it hogs a processor 100% while the application is open, switching processors as it goes along.
After exiting the program, all returns to normal.

Steps to Reproduce:
1.Start computor, Ubuntu Linux 14.04
2.Start LibreOffice 6
3.Open System Monitor
4.Observe Resources..

Actual Results:
A processor is running at 100%

Expected Results:
Very little processor involvement when program is not being used?


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Kobus 2018-11-01 10:35:50 UTC
Created attachment 146218 [details]
Resource screen shot
Comment 2 Kobus 2018-11-01 10:36:47 UTC
Created attachment 146219 [details]
Process screen shot
Comment 3 Kobus 2018-11-01 10:37:22 UTC
Created attachment 146220 [details]
My Hardware
Comment 4 Xisco Faulí 2018-11-12 14:42:12 UTC
Thank you for reporting the bug. To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 5 Kobus 2018-11-12 16:43:06 UTC
Created attachment 146572 [details]
New Process Screenshot

After resetting my User Profile, the problem is still present, as per new screenshot
Comment 6 Xisco Faulí 2019-05-16 11:46:16 UTC
A new major release of LibreOffice is available since this bug was reported.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 7 QA Administrators 2019-11-13 03:34:15 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2019-12-14 03:41:45 UTC
Dear Kobus,

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