Download it now!
Bug 129420 - Decrease performance when select many aleatory cells with Ctrl pressed.
Summary: Decrease performance when select many aleatory cells with Ctrl pressed.
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.0.7.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Cell-Selection gtk3-whipping-boy
  Show dependency treegraph
 
Reported: 2019-12-15 21:14 UTC by Yerinier Ferrás
Modified: 2019-12-19 09:08 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Processor Doing Some Hard Work, when 30 cells are selected randomly. (281.07 KB, image/png)
2019-12-18 00:14 UTC, Yerinier Ferrás
Details
Flamegraph (with gtk3 rendering) (47.49 KB, application/x-bzip)
2019-12-18 20:33 UTC, Julien Nabet
Details
Flamegraph (with gen rendering) (40.51 KB, application/x-bzip)
2019-12-18 20:39 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yerinier Ferrás 2019-12-15 21:14:41 UTC
Description:
If you keep the Ctrl key pressed to select for example alternate cells (A1,A3,...,A9,B2,B4,...,B10,C1,C3,...,C9,D2,D4,...,D10, And so on)
Eventually at certain point LibreOffice Calc slows down this process to the point is almost impossible to select anymore or do something else in the app.

This problem happened to me when I tried to do the simulation in this video: https://www.youtube.com/watch?v=VVQZ7QPWoh8
Then I reproduced this problem in a blank document selecting aleatory cells.

Steps to Reproduce:
1.Open LibreOffice Calc.
2.Select at least more than 10 aleatory cells.
3.That's all.

Actual Results:
The process of keeping selecting cells becomes slowly to the point is almost impossible to continue. 

Expected Results:
The application must select cells in a fluent way, no matter how you selected. 


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Linux (Linux Mint 19.2 Cinnamon)
OS is 64bit: yes
-----------------------------------
[Help - About LibreOffice]
Version: 6.0.7.3
Build ID: 1:6.0.7-0ubuntu0.18.04.10
CPU threads: 16; OS: Linux 5.3; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: CL
-----------------------------------
[Other information about SO and HW]
Linux Kernel: 5.3.0-24-generic
Processor: AMD Ryzen 7 1700 Eight-Core Processor × 8
G.Card: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X]
------------------------------------
[The entire output of 'glxinfo | grep OpenGL']:
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Radeon RX 560 Series
OpenGL core profile version string: 4.6.13572 Core Profile Context
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.13572 Compatibility Profile Context
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: 4.6.13572 Compatibility Profile Context
OpenGL ES profile shading language version string: 4.60
OpenGL ES profile extensions:
Comment 1 Julien Nabet 2019-12-16 09:31:54 UTC
Could you give a try to a recent LO version?
Last stable one is 6.3.4.
Comment 2 Yerinier Ferrás 2019-12-16 23:06:34 UTC
(In reply to Julien Nabet from comment #1)
> Could you give a try to a recent LO version?
> Last stable one is 6.3.4.

I tested the same scenario described in 'Steps to Reproduce' section, now using LibreOffice 6.3.4, and the problem persist.
Comment 3 QA Administrators 2019-12-17 03:27:17 UTC Comment hidden (obsolete)
Comment 4 Julien Nabet 2019-12-17 08:00:50 UTC
For the test, could you do this:
- launch term/console
- type:
export sal_use_vclplugin=gen && soffice --calc

Then try to reproduce the pb.

The goal is to know if it concerns only gtk3 rendering or not.
Comment 5 Roman Kuznetsov 2019-12-17 12:41:39 UTC
(In reply to Julien Nabet from comment #4)

> 
> The goal is to know if it concerns only gtk3 rendering or not.

It may be Ubuntu build problem

Yerinier, please try install LibreOffice from libreoffice.org, not from PPA or repo of your OS.
Comment 6 Julien Nabet 2019-12-17 13:12:39 UTC
(In reply to Roman Kuznetsov from comment #5)
> (In reply to Julien Nabet from comment #4)
> 
> > 
> > The goal is to know if it concerns only gtk3 rendering or not.
> 
> It may be Ubuntu build problem
> 
> Yerinier, please try install LibreOffice from libreoffice.org, not from PPA
> or repo of your OS.

I never advise to try Linux LO packages from libreoffice.org because you never know if dependencies will be ok. IMHO, these should be just for packages maintainers or those who are interested in tweaking.
Comment 7 Yerinier Ferrás 2019-12-18 00:12:33 UTC
(In reply to Roman Kuznetsov from comment #5)
> (In reply to Julien Nabet from comment #4)
> 
> > 
> > The goal is to know if it concerns only gtk3 rendering or not.
> 
> It may be Ubuntu build problem
> 
> Yerinier, please try install LibreOffice from libreoffice.org, not from PPA
> or repo of your OS.

Hi Roman,
Before I installed the latest version (6.3.4), I purged all packages from version: 6.0.7.3. Then I installed version 6.3.4, from: https://mirror.ueb.edu.ec/tdf/libreoffice/stable/6.3.4/deb/x86_64/LibreOffice_6.3.4_Linux_x86-64_deb.tar.gz

Now I executed 'export sal_use_vclplugin=gen && soffice --calc' (as Julien Nabet suggested) bu in this way: 
export sal_use_vclplugin=gen && /opt/libreoffice6.3/program/soffice.bin --calc

I tested the scenario many times, and the same result. During my tests I noticed that the fan cooler of my processor was increasing the sound. Then I opened the System Monitor App and put it side by side in the descktop with LO Calc. I performed the test a couple times and I taked a screen picture (attached to this issue), as You can see for one minute and more  the porcessor is doing something many times. This happened when I selected a least 30 cells in alleatory way.
Comment 8 Yerinier Ferrás 2019-12-18 00:14:52 UTC
Created attachment 156639 [details]
Processor Doing Some Hard Work, when 30 cells are selected randomly.
Comment 9 Yerinier Ferrás 2019-12-18 00:19:57 UTC
Comment on attachment 156639 [details]
Processor Doing Some Hard Work, when 30 cells are selected randomly.

Para cuando esta captura de pantalla se tomó la aplicación todavía no había terminado de renderear el resto de las celdas seleccionadas.

The application was launched from terminal using the following line:
export sal_use_vclplugin=gen && /opt/libreoffice6.3/program/soffice.bin --calc
Comment 10 Yerinier Ferrás 2019-12-18 00:23:32 UTC
Comment on attachment 156639 [details]
Processor Doing Some Hard Work, when 30 cells are selected randomly.

By the time this screenshot was taken, the application had not yet finished rendering the rest of the selected cells.
Comment 11 Julien Nabet 2019-12-18 20:28:24 UTC
On pc Debian x86-64 with master sources updated today, I could reproduce this.
Comment 12 Julien Nabet 2019-12-18 20:32:09 UTC
Kohei/Lubos: following your discussion about Calc perf, thought you might be interested in this one.
Indeed, I just launched Calc, then selected A1, A3, A5, etc.
After 25 cells, it began to become a bit slow then at 30 it's really slow (I got a Ryzen 5 + 32Go with no other running apps except "usual" services on a Debian testing)

I'm gonna attach a Flamegraph

Of course don't hesitate to uncc yourself if not interested, no time, or anything.
Comment 13 Julien Nabet 2019-12-18 20:33:23 UTC
Created attachment 156655 [details]
Flamegraph (with gtk3 rendering)
Comment 14 Julien Nabet 2019-12-18 20:39:31 UTC
Created attachment 156656 [details]
Flamegraph (with gen rendering)

Argh, I don't reproduce the slowdown with gen rendering. I selected 40 cells, nothing special.

Since this rendering doesn't call accessible part (the part which seems to consume a lot of cpu with gtk3 rendering), it's understandable.
So it means no mdds issue here.
Comment 15 Roman Kuznetsov 2019-12-19 04:59:39 UTC
Caolan, can you look at it?
Comment 16 Caolán McNamara 2019-12-19 09:08:23 UTC
Its an accessibility problem, rather than a specific gtk3 problem.If a11y was working in an alternative backend the same thing will happen.