Description: When selecting SAVE icon or MEUN--> SAVE in a spreadsheet--in this case approx. 900 rows and about 20 cols, I get a spinning pinwheel lasting 7-15 seconds. Also noting memory problems persisting after SAVE Steps to Reproduce: 1.Use a decent size spreadsheet 2. click save or Menu save 3. Actual Results: I get a spinning pinwheel lasting 7-15 seconds. Also noting memory problems persisting after SAVE Expected Results: instantaneous save with no pinwheels or save delays. Reproducible: Always User Profile Reset: Yes Additional Info: This is a CRITICAL bug and needs immediate attention as it impacts performance and system resources and not released. Systems parameters: Using Libreoffice for MAC silicon v. 24.2 in Apple Mac M3 w. 32g RAM running latest MAC OS Sonoma 14.5. This issue has existed in prior libre versions (including the official libreoffice version) and noticed as well in prior MAC OS versions. Lastly, the Libre profile safe mode resetting was done and it did NOT fix this situation.
Thank you for the report. Sounds similar to bug 160286. Could you please test version 24.2.3, as it includes some macOS memory bug fixes? Thank you!
I am using 24.2.4.2 and still the issue exists. It appears to be driven by whenever a spreadsheet has conditional formatting or code in place in rows that the spinning wheel occurs on saving. The wait time is significant and should never be the case on my M3 32g Macbook Pro.
Same issue as orginal ticket below and issue persists in newest release 24.2.4.2 This should be raised to MAJOR issue however, I am not allowed to make that change in this ticket. Much Thanks.
(version changed back to original one, as the field is for "earliest affected" version) (status set to "unconfirmed" as "reopened" is for specific cases: only for when a report was previously set as "fixed") Thanks for testing again. - What do you mean by "code in place in rows"? - Are you able to attach a sample document, so others can test in the same conditions? Thank you.
Considering patches already committed to the Dev builds for tdf#161461 and for tdf#159175, I would suggest following (for example) tdf#159175 comment19 (especially the "xattr" command). At any rate, please report back here in tdf#160860 (not in the other tickets).
(In reply to ady from comment #5) > At any rate, please report back here in tdf#160860 (not in the other > tickets). Was that text I am quoting too difficult to understand? The patches in the aforementioned reports will be available in the next LO 24.2.5 and also in the next 24.8 and 25.5 branches. This is also mentioned in the links I posted before – just needs a minor simple reading (of only one comment). Please either report here in tdf#160860 your tests with the Dev versions, or wait for those versions to be released. At any rate, there is no way to know whether the new versions will effectively solve the reported problem, unless it is tested and reported back here.