Description: When I open a file(3,028KB) with 5500 rows and A to O columns using calc, it takes 30 seconds. Saving the file will take 35 seconds. This file has comments inserted into many cells. Due to the automatic save function added in Ver.24.2.0.3, I am often forced to interrupt my work for long periods of time. This phenomenon does not occur in files without comments in cells. Bug 76324 is similar, but the status is marked as fixed. But I think the fix is not enough. Please continue to make corrections. This experiment was performed on AMD Ryzen 7 5800H + NVMe SSD best regards. Steps to Reproduce: 1.Using Calc,make new ods file. 2.Insert comment to A1 cell,and input character 'a' to this comment. 3.Copy A1 cell to ALL cell A1 to O5500. 4.Save this file. Actual Results: The save process will not end until 30 seconds have passed. During this time, no work will be possible. Expected Results: I want the save process to finish within ten seconds. Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: CL threaded
If this is not new behaviour in 24.2, I would close this as a duplicate of bug 125619. Do you agree?
(In reply to Buovjaga from comment #1) > If this is not new behaviour in 24.2 The problem is probably not a new one – not that I have tested it – but I assume that the behavior is now seen more promptly because the automatic backup save was re-enabled with LO 24.2. From the Release Notes for 24.2 (Core / General): * "Save AutoRecovery information" * "Always create backup copies" * Fixed many AutoRecovery limitations and re-enabled AutoSave UI
I saw the thread for bug 125619 as pointed out by Buovjaga san. But I don't think it should be integrated with threads for bug 125619. As far as I can confirm on my PC, the cause is not an abnormal load on the CPU. This is because while saving and opening files, the CPU load displayed in the task manager only reaches about 10% at most. However, I would like to report that the CPU clock is boosted to 4GHz during the save process. It also doesn't seem like there's a memory shortage. This is because there is more than 8GB of free area out of the 16GB of installed memory. The situation is different from bug 125619, although they share the same problem: problems with saving and opening files that contain a large number of cells with comments inserted.
(In reply to mizif034 from comment #3) > I saw the thread for bug 125619 as pointed out by Buovjaga san. > But I don't think it should be integrated with threads for bug 125619. > As far as I can confirm on my PC, the cause is not an abnormal load on the > CPU. > This is because while saving and opening files, the CPU load displayed in > the task manager only reaches about 10% at most. > However, I would like to report that the CPU clock is boosted to 4GHz during > the save process. > It also doesn't seem like there's a memory shortage. > This is because there is more than 8GB of free area out of the 16GB of > installed memory. > The situation is different from bug 125619, although they share the same > problem: problems with saving and opening files that contain a large number > of cells with comments inserted. Saving is not multi-threaded, so 10% on your machine seems to be in line with bug 125619. The load is abnormal in this context. The cause itself is known in any case, but unfortunately as discussed in bug 125619 it would require "a fairly major refactoring of how comments/notes work in Calc". *** This bug has been marked as a duplicate of bug 125619 ***