Bug 128586 - Each inserted Shape with Gradient Filling blocks UI for a while after Open, Save and Close operations.
Summary: Each inserted Shape with Gradient Filling blocks UI for a while after Open, S...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1.5.2 release
Hardware: ARM Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-04 12:24 UTC by Juanma
Modified: 2020-06-04 03:44 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 Juanma 2019-11-04 12:24:40 UTC
Description:
When opening, closing or saving odt documents, containing Shapes with gradient infills, gets 100% cpu use for the main thread and blocks the UI for an unreasonable amount of time.

Steps to Reproduce:
1.Create a new blank Writer document
2.Insert any text
3.Save the file and make note of the time it took to give back UI control. 
4.Insert any Shape using "Menu->Insert->Shape->Basic->Rectangle"
5.Change the propertie "Fill" from "Color" to "Gradient", but do not change any other properties.
6. Save the file and make note of the time it took to give back UI control. 
7. Make many copies for the new shape and place them any where in the document.
8. Save the file and make note of the time it took to give back UI control. 

Actual Results:
3. The save operation in this step should be instantaneous.
6. It is noticeble an unusual delay. The procesor gets 100% use before returning the control to the UI.
8. The delay of the operation seems proportional to the number of shapes created. The time to gat back the control to the UI starts to be ureasonable long.


Expected Results:
The open, Close and Save operations shoud be reasonable quick and proportional to the amount of data saved.
Shapes with gradient infill should not affect unreasonably the CPU utilization of the application.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Computer
==================
Hardware:         Raspberry Pi 4
Operating System: Raspbian GNU/Linux 10 (buster)
Kernel:           Linux 4.19.75-v7l+
Architecture:     arm

About Libreoffice
=================
Version:          6.1.5.2
Build ID:         1:6.1.5-3+rpi1+deb10u4
CPU threads:      4; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale:           en-GB (en_GB); Calc: threaded
Comment 1 Xisco Faulí 2019-11-05 11:40:24 UTC
Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
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 2 QA Administrators 2020-05-04 03:43:18 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2020-06-04 03:44:49 UTC
Dear Juanma,

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