Bug 142782 - GTK3: LO 7.2 Alpha1 starts very slowly
Summary: GTK3: LO 7.2 Alpha1 starts very slowly
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.2.0.0 alpha1+
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-11 07:01 UTC by Stéphane Guillou (stragu)
Modified: 2021-06-12 11:08 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 Stéphane Guillou (stragu) 2021-06-11 07:01:27 UTC
Description:
Starting any component of LibreOffice takes a lot more time than usual, but starting soffice with this extra option takes a normal amount of time:

soffice -env:SAL_USE_VCLPLUGIN=gen 

Which suggests it is an issue which affects GTK3 systems (as I have been told).

Steps to Reproduce:
1. Start a LibreOffice component, for example Writer

Actual Results:
The component takes too long to be operational (about 30 seconds on my computer) and hangs long enough to have "does not respond" dialogues popping up.

Expected Results:
The component opens in a normal amount of time (max 2 seconds on my computer).


Reproducible: Always


User Profile Reset: No



Additional Info:
I started noticing the issue with:

Version: 7.2.0.0.alpha1+ / LibreOffice Community
Build ID: 17694c906f94a195a2d5086e0e87afa1c852107b
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-06-09_20:52:06
Calc: threaded

And it was not an issue with a build from just a few days before (not sure which one, sorry), so the change must have happened very recently.
Comment 1 Buovjaga 2021-06-11 12:22:40 UTC
Not seeing the GTK3 slowness in the latest commit of linux-64-7.2 bibisect repo, which is from Thu Jun 10 09:07:03 2021 +0200

Maybe you could also try with --safe-mode command line option and continuing in safe mode. If the user profile has stayed the same.
Comment 2 Stéphane Guillou (stragu) 2021-06-12 10:11:34 UTC
OK, a profile reset fixed it... Thanks Buovjaga. I should take that more seriously when testing! What kind of status should we use to close the bug?