Bug 134047 - Start Center: Massive Slowdown when orphaned links exists
Summary: Start Center: Massive Slowdown when orphaned links exists
Status: RESOLVED DUPLICATE of bug 131850
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2020-06-16 17:52 UTC by bugzilla2
Modified: 2020-06-17 08:07 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description bugzilla2 2020-06-16 17:52:53 UTC
In LibO 6.4, the Start Center starts extremely slow, when there are links to files that does no longer exist, most of all, when those files were on a network share. Regression, as this slowdown didn't exist up until 6.3 series.

Steps to Reproduce:
1. Install/use LibO 6.3 series
2. Place a Document on a Networkshare and open it in LibO 6.3
3. Open the Start Center (it should start with normal speed and list the file that was opened before)
4. Delete the file from the network share
5. Upgrade to LibO 6.4.4
6. Launch Start Center

Actual Results:
Start Center starts very slowly (10 Seconds instead of less then a half, with 3 missing files)

Expected Results:
Start Center should launch as fast as in 6.3 series

Reproducible: Always

User Profile Reset: No

Additional Info:
On the system where I recognized the problem, there were 3 missing files linked in start center, two of them were on a server that is no longer available. Broken links to files on the local system seem to have no (noticeable) impact. I guess this all is because of the introduction of Application-Icons on the Thumbnails. Seems like the function calls the file to create the overlay, instead of just use the file-extension to determine the right icon.
Comment 1 Telesto 2020-06-17 06:49:26 UTC
Any change to bibisect this.. needs a bit of specific environment to reproduce..

Comment 2 Maxim Monastirsky 2020-06-17 08:07:38 UTC

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