If I create a new spreadsheet, I do not see any beach balls and I can do all of the things.
From about 15-20 seconds and a few random operations / clicks after I save it, a wild beach ball appears!
However, sometimes creating a new spreadsheet will give a beach ball right away. Hard to determine what conditions are necessary for repeating that at this point. Seems random.
Now, neither Mac runs Libreoffice but there is a common element.
I wonder why you would use a third party uninstaller with generic rules rather than the uninstall procedure that comes with the program and can be initiated with standard operating system uninstall procedure
The question this immediately raises is, okay then so you are a Mac user that is not experiencing any of the problems described here?
Because, to answer your question, it should be obvious that CleanMyMacX would promise to Clean My Mac (X), i.e. do a thorough job of uninstalling where a normal uninstaller may only do a partial job (as they often do). I’m not entirely trying to be snarky here, but I fail to see how using a third party uninstaller would make anything any worse. In my experience, CleanMyMacX mainly just deletes leftover launchd stuff. I, personally, use it simply out of habit, but ok.
Alright, I move /Applications/LibreOffice.app to the trash, reinstall, re-grant Full Disk Access, run, Open, Descriptive Statistics, click, annnnnnd beach ball.
If you are indeed another Mac user, would you be willing to try uninstalling via Finder yourself and see how you fare?
For what it’s worth I’ve got plans to reinstall MacOS entirely in the coming days so there’s that as well.
I’m not using macOS myself, and thus not being familiar with specifics of installation process there, I suppose, @EarnestAl might base their comment on known problems that similar tools create on Windows OS (we even have explicit mention on FAQ, asking to not use third-party tools claiming to cleanup leftovers, or otherwise replace standard uninstallers, on Windows). Note that even if “it should be obvious that CleanMyMacX would promise to”, it is still not obvious that it would fulfil its promise: all the tools that create grief on Windows, also promise wonders :).
Of course, it might be not applicable to macOS, but I believe it’s a honest attempt to understand the reasons of details that look not obvious, in something giving problems - and thus is not deserving even a slightly snarky attitude 
If you can see that honest attempt then you can also see an honest attempt by me at moving past that and actually answering his question:
Alright, I move /Applications/LibreOffice.app to the trash, reinstall, re-grant Full Disk Access, run, Open, Descriptive Statistics, click, annnnnnd beach ball.
If you are indeed another Mac user, would you be willing to try uninstalling via Finder yourself and see how you fare?
That last question I would pose to any Mac user willing to jump in. Because yes, it does seem plausible that something could very well be happening during the installation / uninstallation process, especially because 7.1.3.2 was working just fine for me at one point but now that particular version does not, which is very odd.
Since being able to use LibreOffice on Mac is very important to me, I am going to go ahead and submit a bug report myself. But before I do so, I have a few questions:
I have now gone all the way back to version 7.0.0.1 and I’m seeing beach balls now with versions I know have been without them before. Granted, I was mostly on Catalina back then. So I’m thinking that this may just be an issue that was introduced with with Big Sur. More precisely, I surmise it was in 11.6.4, as LO was not exhibiting this behavior in earlier versions of MacOS. For me, at least, but it seems @Marcus_SC has been enduring this for a much longer time.
If XCode works for you, just use it. AFAIK, those who develop on macOS do use it.
I don’t think that using MacPorts is the way to go … you better use the source code from the project, not some third-party version.
Just join #libreoffice-dev, and ask your questions there. We badly need developers on macOS.
I’d be happy to step in as a MacOS dev. I cannot commit to a whole lot of time, but I do love the software, and as I said it’s very important to me to be able to use it on MacOS. This is one way I can help ensure that it keeps rolling along!
Well after much in the way of what I would consider to be preliminary testing, it seems the workaround for 7.3.2.2 seems to be to simply to restart in Safe Mode, and be sure to choose “Reset to factory settings”. The checkboxes underneath may or may not also help. But this is the best I’ve got right now for something that may or may not make LO usable again.
And besides obviously not being something that users should be expected to do, I’m not sure the long-term effects of relying on such a workaround, but until a fix can be found, I am just going to have to use it. And use it I will, because I use LO at least weekly.
Even still, beach balls do show up from time to time. For example just now, as I opened a document, did my Descriptive Statistics thingie, and ⌘Q’ed, I got a beach ball and had to Force Quit. And earlier, I tried to maximize the window and once again got the bottom-right corner to expand followed by a beach ball (no top-left).
Furthermore, even after deleting my user profile (which really is the whole point of trying safe mode), beach balls are just everywhere, even with Full Disk Access enabled. This is clearly a bug and not just profile corruption.
Anyway, it sounds like my work’s cut out for me. Hopefully I can get to the bottom of this soon.
Well I just finished reinstalling MacOS, I’ve got 7.3.2.2 installed, and it seems that at least the problems I described in this thread have gone away and I am seeing no beach balls (yet) and I have not enabled Full Dask Access (yet).
@Marcus_SC you did say you have reinstalled but still get beach balls. Can you describe how to reproduce the error step by step?
[quote=“hexadecagram, post:22, topic:75896”]
, sometimes creating a new spreadsheet will give a beach ball right away. [/quote]
.
.
Similar here.
Sometimes.
Hi @hexadecagram @Marcus_SC @ksdavidc! Mac user here, same problem on macOS Monterey (I skipped Big Sur), running LO 7.3. Several years ago (can’t remember which macOS) freezings occurred every now and then, but now LO has become utterly unusable on macOS (On Mac: LibreOffice keeps crashing) if factory settings remain unchanged.
What has helped me, I think, is simply turning OFF
Load/Save > General
Save AutoRecovery information every: [X] minutes
Freezings still occur but a less often. I am now able to work one or even two hours without having to Force Quit LO. https://bugs.documentfoundation.org/show_bug.cgi?id=146598#c11
@jeshkhol Yeah, I had the same result. stopping autosave 
did seem to improve it…for now. will keep watching…
Run in safe mode, wait. Beach balls WHILE IN SAFE MODE!
Leave nearly blank brand new 4-character project open for 20 min with no user interaction, return: Beach Ball
Copy text and try to copy into Chrome: Both Chrome and LO give beachballs.
Even turning off autosave is not working anymore for me.
I am taking bets this has zero to do with any particular user action. It is happening in the background, so can show up at any time.
Thank you @hexagram for taking the steps you are taking.
@ksdavidc The spinning wheel still occurs frequently here as well, despite autosave being turned off. What seems to help often is to wait a few seconds after selecting and copying items, i.e. before clicking into a different app (or even into a different cell in Calc).
Also, I musn’t double-click in the Finder to open a file if LO isn’t already running, or else the spinning wheel occurs. So I always need to start LO before trying to open a file.
I manually save (Cmd-S) several times a minute, especially before selecting anything, which means that I haven’t lost any data so far. I’m not sure yet how to best deal with the File Recovery dialogue – sometimes I need to click Discard in order to keep the spinning wheel from reocurring, sometimes I need to recover the files for the same reason.
In other words, working with LibreOffice on macOS Monterey is possible despite the frequent hangings. However, constantly having to deal with these hangings is enormously time-consuming, and therefore I currently cannot recommend anyone to use LibreOffice on a Mac. This will change as soon as these hangings don’t occur any more because LibreOffice is very powerful.
@hexagram, thanks for working on this. I have saved many dozens of error reports related to these hangings over the past few weeks so let me know if you think they could be useful.
@jeshkhol Thanks for the tips, I will definitely try them. Yeah, I am using Pages as what I hope will be a temporary alternative, but for some things that doesn’t work. I got the computer specifically so I could port my work to a faster computer, so for me it’s definitely a let down, but i like LO and have hope it may get sorted.
Where would I find the error reports/logs/flags/diagnostics/ what have you? I would be more than glad to send them along if that might help. I am currently testing 7.0.6 to see if a very old version will work. I need something…
7.0.6 no go, but:
Turning off JAVA seems to have helped!! It’s a new machine and no jre is installed. Could that be it???..
I spoke too soon. D**n
addendum: well, not so bad, it did crash, but no beach ball. working for now. will see…
Maybe @hexagram can suggest where to send crash reports to?
If you haven’t yet done so, please add your voice to the bug database (https://bugs.documentfoundation.org/show_bug.cgi?id=146598) since developers who may be able to fix this will look there rather than here. The more Mac users report experiencing the same freezing problem, the earlier dealing with this bug may be prioritised.
please add your voice to the bug
You are welcome to comment on bugs constructively, but please don’t add any “me too”-like comments that only make bugs unmaintainable. Comment count is not used as priority marker; any comment is only useful if it helps to fix the bug (e.g., adds something substantial missing in prior comments: like specific repro steps).
OTOH you are welcome to CC yourself to bugs - CC count is definitely one of priority markers that we use.
let machine unattended with 4 files open for 6 hours. came back to beachballs.
Also, just reinstalled and opened and then closed. Got the recovery screen with NO files!! recover that LO!!
I posted first on the bug site, then found this. AM going to update the bugs site with whatever information I do find. I am positing here to help anyone else who might encounter this…