Bug 144708 - Recent documents repeated use slows LO to crawl
Summary: Recent documents repeated use slows LO to crawl
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.2.1.1 rc
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: perf
Depends on:
Blocks: Performance
  Show dependency treegraph
 
Reported: 2021-09-24 17:20 UTC by Ari Latvala
Modified: 2023-01-02 08:09 UTC (History)
3 users (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 Ari Latvala 2021-09-24 17:20:00 UTC
When opening and closing any file or files from "Recent documents" view, LO starts to slow down after ca. 15 cycles of opening and closing file(s). CPU threat shows high usage for LO and LO starts to show longer and longer "Not responding". To fix the problem LO needs to be shut down and restarted.
Comment 1 m_a_riosv 2021-09-25 11:08:11 UTC
Please test with a clean profile, Menu/Help/Restart in Safe Mode
Comment 2 Ari Latvala 2021-09-25 11:51:25 UTC
Exactly same behavior on LO Safe mode now that I tested it using LO 7.2.1 on Windows 10 with all the latest updates in place. Created a new LO Writer doc just one word on it, saved, then closed and re-opened it for multiple times. Around 15th time slowdown was already very clear and comes worse at every run, both opening and closing the document. Even closing LO takes at that point quite some time.
Comment 3 m_a_riosv 2021-09-25 16:48:44 UTC
Confirmed, LO becomes more and more slow, it happens about 16 cycles save/Load.
Seems the options Menu/Tools/Options/Load&Save/General - Save autorecovery and Always create backup doesn't affect here.

Version: 7.2.2.1 (x64) / LibreOffice Community
Build ID: 0e408af0b27894d652a87aa5f21fe17bf058124c
CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL
Comment 4 m_a_riosv 2021-09-25 17:01:32 UTC
I test up 32 times without problem with
Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 7cd5b35caa8d4fa9d0ba2b2c6ce4b88726ed2be6
CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL

Perhaps not so easy to find the change that solves the matter, but it's near to a year before 7.3 is released.
Comment 5 Telesto 2021-09-27 19:30:13 UTC
(In reply to m.a.riosv from comment #3)
> Confirmed, LO becomes more and more slow, it happens about 16 cycles
> save/Load.
> Seems the options Menu/Tools/Options/Load&Save/General - Save autorecovery
> and Always create backup doesn't affect here.
> 
> Version: 7.2.2.1 (x64) / LibreOffice Community
> Build ID: 0e408af0b27894d652a87aa5f21fe17bf058124c
> CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Vulkan; VCL:
> win
> Locale: es-ES (es_ES); UI: en-US Calc: CL

Also after profile reset?
Comment 6 Buovjaga 2022-01-04 16:06:36 UTC
Bug 131850 was fixed. The fix went into the versions 7.4.0, 7.3.0.0.beta2 and 7.2.5. Could you re-test with a new version? 7.2.5 will be released soon: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.5_release
Comment 7 BogdanB 2022-12-29 06:05:07 UTC
Need retesting here for meanwhile improvements.
Comment 8 Ari Latvala 2023-01-02 08:04:10 UTC
Tested by opening and closing document for ca 50 times, no problems detected:
Version: 7.4.3.2 (x64) / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: fi-FI (fi_FI); UI: en-US
Calc: threaded

Device name	Lenovo W530
Processor	Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz   2.60 GHz
Installed RAM	32,0 GB (31,6 GB usable)
System type	64-bit operating system, x64-based processor
Pen and touch	No pen or touch input is available for this display
Comment 9 Buovjaga 2023-01-02 08:09:06 UTC
Kiitos perusteellisesta testaamisesta! / Thanks for testing! Let's change to worksforme as we can't be 100% sure of the fix.