Bug 144972 - very slow LibreOffice writer start
Summary: very slow LibreOffice writer start
Status: RESOLVED DUPLICATE of bug 131850
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.1.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-06 19:13 UTC by george
Modified: 2021-10-22 03:47 UTC (History)
0 users

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 george 2021-10-06 19:13:06 UTC 
Description:
I noticed that, despite upgrading to a NVMe SSD, LibreOffice Writter was too slow to start (almost 10 seconds). After several tries to rectify the problem, I discovered that the problem was caused from recent files list, which included files that no longer exist or couldn't be accessed. Clearing the recent files, allowed LibreOffice Writter to open in under 2 seconds!

Steps to Reproduce:
1. Try open several libreoffice files, then delete them. Open files from external sources, then disconnect external sources.
2. Open LibreOffice


Actual Results:
A full "recent files" list with files that no longer exist or can't be accessed, causes LibreOffice to start very slow.

Expected Results:
LibreOffice starts very slow


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.2.1.2 / LibreOffice Community
Build ID: 20(Build:2)
CPU threads: 16; OS: Linux 5.11; UI render: default; VCL: gtk3
Locale: el-GR (en_US.UTF-8); UI: en-US
Ubuntu package version: 1:7.2.1-0ubuntu0.20.04.1~lo1
Calc: threaded


[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Comment 1 Michael Warner 2021-10-21 13:17:57 UTC 
Hello George,

Thanks for your bug report. Unfortunately, this is a long-standing issue. See bug 101302 and bug 131850.

*** This bug has been marked as a duplicate of bug 131850 ***