Bug 163445 - LO 24.8.2 takes exceedingly long time to start with SLES 15 SP5
Summary: LO 24.8.2 takes exceedingly long time to start with SLES 15 SP5
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
24.8.2.1 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Performance
  Show dependency tree / graph
 
Reported: 2024-10-15 14:21 UTC by Eyal Rozenberg
Modified: 2025-02-20 16:20 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eyal Rozenberg 2024-10-15 14:21:13 UTC 
I've installed LO 24.8.2.1 on a SLES 15 SP5 GNU/Linux system, using the downloadable RPMs.

When I invoke it after installation, it takes about a full minute for the splash screen progress bar to complete, and for the start center to come up. This does not improve when restarting.

No error message or terminal output appears about any problem.

Note: I'm using a remote X session. Build info:

Version: 24.8.2.1 (X86_64) / LibreOffice Community
Build ID: 0f794b6e29741098670a3b95d60478a65d05ef13
CPU threads: 80; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: CL threaded
Comment 1 Buovjaga 2025-02-18 15:36:35 UTC 
(In reply to Eyal Rozenberg from comment #0)
> Note: I'm using a remote X session. Build info:

So what about a non-remote session?
Comment 2 Eyal Rozenberg 2025-02-20 16:17:44 UTC 
(In reply to Buovjaga from comment #1)
> So what about a non-remote session?

Sorry, the machine I was using has been reformatted with a different distribution. You can close this if you like.
Comment 3 Buovjaga 2025-02-20 16:20:06 UTC 
Ok. For deep research, one could compile LibreOffice with --enable-symbols (instead of any debug option) and then capture and graph a perf trace: https://wiki.documentfoundation.org/Development/How_to_debug#Performance_debugging_(perf)