Description: Hi, I've been having an issue with Libre Office on my Mac M1 Pro since i bought it about 6 months ago, both writer and calc have an issue where they will lockup and i get the colour spinning wheel. This seems to be most frequent if i leave either application open for a long period of time or have them open and the computer sleeps and awakens, but also happens randomly. Reading through previous support on the forums I have provided full disk access, disabled skia and on the las tupdate i removed and reinstalled it entirely with no luck. I am more than happy to post logs/reports if someone can help guide me. Thanks Steps to Reproduce: 1.Open a calc or writer document and leave open 2.Close the computer lid or put it to sleep 3.Go back to Libreoffice and try to start editing the document, repeat 1-3 and it will eventually crash Actual Results: Libreoffice freezes and I see the spinning colour wheel indefinitely. Libreoffice must be force quit at that point. Expected Results: Libreoffice should of just allowed editing from where the user left off without crashing. Reproducible: Sometimes User Profile Reset: Yes Additional Info: Version: 7.3.4.2 / LibreOffice Community Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5 CPU threads: 8; OS: Mac OS X 12.4; UI render: default; VCL: osx Locale: en-CA (en_CA.UTF-8); UI: en-US Calc: threaded
When you force quit, can you follow the steps here to collect a bug report: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#macOS:_How_to_get_debug_information Don't send the report to Apple, just save it to a file and attach it to this bug report. Thanks.
Created attachment 181466 [details] Crash Report Hi Michael, Thanks for the instruction, crash report attached.
[Automated Action] NeedInfo-To-Unconfirmed
Created attachment 181478 [details] Crash Report 2 - Writer Here is another crash report in writer, this occurred when trying to copy and paste from one file (.docx) to another file (.odt) - occurred every time (tried 5x after force quitting) until I rebooted the machine. I hope this helps track down the issue.
@Shaun : there are a lot of accessibility API calls in that 2nd trace, and it seems that there is a mutex lock on a call waiting for a response (possibly on an accessibility function). I also see the calls to the font dropdown menu - would this be the font preview function in LO? Are you using any kind of accessibility feature at the OS level, e.g. Voiceover, screen magnification, or other separate accessibility tool ?
For example, all of this stuff: VCLXAccessibleToolBox::getAccessibleChild(int) + 356 (libacclo.dylib + 559388) [0x2b4b0c91c] 15 vcl::Window::GetAccessible(bool) + 88 (libvcllo.dylib + 142908) [0x10483ae3c] 15 (anonymous namespace)::SvxFontNameBox_Impl::CreateAccessible() + 92 (libsvxcorelo.dylib + 3512440) [0x1037b5878] 15 lcl_GetDocFontList(FontList const**, (anonymous namespace)::SvxFontNameBox_Base*) + 260 (libsvxcorelo.dylib + 3505184) [0x1037b3c20] 15 FontNameBox::Fill(FontList const*) + 1004 (libsvtlo.dylib + 271508) [0x101f6e494] 15 Idle::Start(bool) + 28 (libvcllo.dylib + 3608420) [0x104b88f64] 15 Task::Start(bool) + 44 (libvcllo.dylib + 3832620) [0x104bbfb2c] 15 std::__1::mutex::lock() + 16 (libc++.1.dylib + 61864) [0x182c991a8] 15 _pthread_mutex_firstfit_lock_slow + 248 (libsystem_pthread.dylib + 7416) [0x182d42cf8] 15 __psynch_mutexwait + 8 (libsystem_kernel.dylib + 18232) [0x182d0d738] *15 psynch_mtxcontinue + 0 (pthread + 9964) [0xfffffe000a55f01c] Could just be a timer scheduling issue in VCL though, wouldn't be the first time.
The only things I can think of that would be along the lines of accessibility are 1) I have an app called "Rectangle" to allow snapping of windows and 2) "Better Touch Tool" to allow custom mappings on the magic mouse. Other than that i dont have anything accessibility related on, i tend to keep my hardware mostly on the default settings. Im not sure about the font preview, at the time of crashing i wasn't doing anything with fonts, so if you can provide some more details about what you mean i might be able to answer.
(In reply to Shaun from comment #7) > The only things I can think of that would be along the lines of > accessibility are 1) I have an app called "Rectangle" to allow snapping of > windows and 2) "Better Touch Tool" to allow custom mappings on the magic > mouse. Other than that i dont have anything accessibility related on, i tend > to keep my hardware mostly on the default settings. > > Im not sure about the font preview, at the time of crashing i wasn't doing > anything with fonts, so if you can provide some more details about what you > mean i might be able to answer. Thanks Shaun, both of those have been reported in the past as causing issues with LibreOffice under some circumstances, often difficult to reproduce. The recommendation here is generally to deactivate / uninstall those tools and try working with LO again to see whether the crash still happens. If it doesn't, problem worked around, and then you will have to decide whether you can live without one or the other, but at least it will enable us to mark this report as a duplicate.
If it's a duplicate, it would be of bug 148435.
Thanks guys, so I've turned both of those tools off and have been playing around and i can still get Libreoffice to crash with similar actions. The difference is now it doesnt hang/freeze, it just immediately crashes - then the window for document recovery pops up on its own. So i dont have the same option to obtain a report unless there is another way to grab a log?
I looked at bug 148435 and there were instruction to use console to possibly get some logs, but libreoffice is not shown in any report section. Reading some other threads it sounds like libreoffice "exits" and restarts?
@Shaun : please try a future 7.5 (developer preview) from the download page - some stuff got fixed in that recently which should limit at least some of the crashing.
I still believe this to be a dupe of https://bugs.documentfoundation.org/show_bug.cgi?id=148435 @Shaun please retry with https://dev-builds.libreoffice.org/daily/master/current.html and let us know if then the issue is persisting.
*** This bug has been marked as a duplicate of bug 148435 ***