Bug 137486 - Window resize of Libre office products result in massive performance decrease as window attempts full re-draw
Summary: Window resize of Libre office products result in massive performance decrease...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.6.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-14 19:59 UTC by Red
Modified: 2022-02-24 03:37 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 Red 2020-10-14 19:59:04 UTC
Description:
As you grab a UI window to resize the content view from the program border, the inner contents in LOCalc UI often display a black window and require a full redraw of the inner UI contents. 

Major machine components affecting results
Gigabyte 1650 Super 4GB,i5-3450S(2.8ghz), 8GB ram

Perceptual Performance in comparison to notepad++ window drag
LibreOffice Calc. 
Perceptual scale: 100% = 60fps, 1%= 1fps or less
All resize operations update on click release or mouse movement stop, unfortunate.

Top left in-20% / out-20%
left in-20% / out-20%
Bottom left in-20% / out-20%
Top in-20% / out-20%
Top Right in-20% / out-20%
Right in-5% / out-5%
Bottom Right in-5% / out-5%
Bottom in-1% / out-1%

Opinion:
The reason I am submitting this, is the delayed update and black window on content resize gives the program(LOCalc) the feel that it is going to crash. It has not, which is great, and more than I can say for Excel. It would be a welcomed update if resizing became smooth as butter.


Steps to Reproduce:
1. Open LibreOffice Calc
2. Hold left click on any border of LibreOffice Calc
3. Drag border and watch window completely re-draw and display sub-standard performance

Actual Results:
The window contents refresh and update at a sub-optimal rate.

Expected Results:
The window contents should have resized the contents of the window at the vertical refresh rate of the monitor.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 6.4.6.2 (x64)
Build ID: 0ce51a4fd21bff07a5c061082cc82c5ed232f115
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: GL; VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: CL
Comment 1 Buovjaga 2021-07-27 11:46:17 UTC
(In reply to Red from comment #0)
> Additional Info:
> Version: 6.4.6.2 (x64)
> Build ID: 0ce51a4fd21bff07a5c061082cc82c5ed232f115
> CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: GL;
> VCL: win; 
> Locale: en-US (en_US); UI-Language: en-US
> Calc: CL

I notice you have OpenGL there, which has been replaced by Skia/Vulkan nowadays. Could you re-test with 7.1.5 or newer?
Comment 2 QA Administrators 2022-01-24 03:35:07 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2022-02-24 03:37:42 UTC
Dear Red,

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