Description: Suddenly, LibreOffice began crashing when I open my manuscript. I upgraded to the latest 6.1.4.2 and it also crashes. OpenOffice does not crash, opens it fine. If I allow LibreOffice to perform recovery, it seems to recover, but crashes as soon as it opens to display the document. There is a very brief moment when it first opens when I can edit the document before it displays the spinning beach ball, but within one or two seconds the ball appears and the Mac says the application is not responding. MacOS 10.13.6 High Sierra, MacBook Pro 15 inch 2016 Steps to Reproduce: 1. Open the document 2. No other action is needed. It crashes within seconds of the screen appears. 3. Actual Results: The spinning beach ball appears within a couple of seconds. The application is dead, unresponsive, and must be forced to quit. I allowed it to wait some 15 minutes in hopes it might recover, but it does not. OpenOffice opens the document fine, and for the moment I am switching to OO. Opens successfully on Windows with version 5.4.3.2, allows edits, then saves and exits without a problem. Upgraded to Windows version 6.1.4.2 to match Mac version. Opens successfully on Windows with version 6.1.4.2, was able to edit, but on save and quit, LibreOffice became unresponsive and the Windows dialog "LibreOffice is not responding" appeared for about 30 seconds or more. But then the dialog closed and LibreOffice finished quitting without problems. So while it seems to have some difficulty, does not crash unrecoverably. Indications are that this may be a Mac-specific issue, but the temporary freeze-up on Windows, which did not happen on the older version, is troubling. Expected Results: This is something the developers should be interested in chasing. I will happily provide the troublesome document to a developer interested in looking at it. (please, treat as if under NDA), but as it is 170+ MB, I will have to provide via Dropbox or direct SCP transfer. Email wa4otj@yahoo.com for additional information. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Restarted in safe mode and opened the same document. It immediately crashed. Restarted in safe mode, disabled OpenGL, opened document. It immediately crashed. Restarted in safe mode, disabled extensions, opened document. It immediately crashed. Version: 6.1.4.2 Build ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3 CPU threads: 8; OS: Mac OS X 10.13.6; UI render: default; Locale: en-US (en_US.UTF-8); Calc: group threaded
Would it be possible you retrieve some backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#macOS:_How_to_get_debug_information)
wa4otj: let me guess, the document in question contains: - multiple frames ? - images within those frames ? - multiple fonts ? - formulae ? - tables (nested or not) ? Anything else we should be aware of ? As Julien has requested, if you could get a backtrace, that would a bit more helpful. Usually, when LO crashes, you should also get the Apple Crash reporter displaying a window with the possibility of sending a report to Apple. Instead of doing that, you can copy the contents of the trace to a simple text file, save that and post it as an attachment to this bug report. Setting to NEEDINFO
Yes, to all of the above, many frames, many pictures. But the frames and pictures count has not changed in a couple of years. Weird. I am attaching a text file with the Apple crash info.
Created attachment 148756 [details] Data reported by Apple dialog
wa4otj: 1) which grammar checker are you using ? 2) do you still experience the same problem if you turn off spellchecking ? I ask this because there appears to be a locked mutex in \ Thread 0x1695be Thread name "GrammarCheckingIterator" 43 samples (1-43) priority 31 (base 31)\ <process frontmost, thread QoS default (requested default), process unclamped, process received importance donation from WindowServer [238], IO tier 0>\ 43 thread_start + 13 (libsystem_pthread.dylib + 11257) [0x7fff7f034bf9] 1-43\ 43 _pthread_start + 377 (libsystem_pthread.dylib + 13581) [0x7fff7f03550d] 1-43\ 43 _pthread_body + 340 (libsystem_pthread.dylib + 13921) [0x7fff7f035661] 1-43\ 43 ??? (<AB77D926-5160-307E-8EA4-0FF9FB943ACE> + 240910) [0x103f6fd0e] 1-43\ 43 ??? (<81CD9EBC-30EF-3A32-89DE-F362B2733950> + 120589) [0x10a71970d] 1-43\ 43 ??? (<81CD9EBC-30EF-3A32-89DE-F362B2733950> + 127615) [0x10a71b27f] 1-43\ 43 ??? (<C338A73F-8E0E-350B-859C-9E819DA3318D> + 5517975) [0x142f31297] 1-43\ 43 ??? (<86B6788B-52AB-3640-B5A6-B3E965DD6FFE> + 4101904) [0x106fd0710] 1-43\ 43 ??? (<AB77D926-5160-307E-8EA4-0FF9FB943ACE> + 203662) [0x103f66b8e] 1-43\ 43 _pthread_mutex_lock_slow + 253 (libsystem_pthread.dylib + 5320) [0x7fff7f0334c8] 1-43\ 43 __psynch_mutexwait + 10 (libsystem_kernel.dylib + 117318) [0x7fff7ee6da46] 1-43\ *43 psynch_mtxcontinue + 0 (pthread + 31325) [0xffffff7f82d15a5d] (blocked by pthread mutex owned by soffice (LibreOffice) [4739] thread 0x1692ad) 1-43\
Grammar checker? Interesting, I only use whatever is default in LibreOffice. I did not install any spell-checking or grammar tools when I installed LO. It has been fine with my document for years. I have been researching and developing this document for over 20 years. I compose my text using Grammarly online and then paste it into LO. I basically ignore LO's grammar and spelling tools for the most part. I just accepted the defaults when I installed LO, so it is whatever... In fact, I find the autocorrect most annoying and have been intending to turn it off. I turned off all spell-checking and grammar and other writing aids in preferences and tried it again. It now opens the document fine, and I was able to save it as a PDF. So it appears as if the spell-checking is related, but it is not clear what changed from two days ago that provoked the crash.
Maybe related to bug 121778 ? Could you please uninstall LibreOffice and install it again downloading it from https://www.libreoffice.org/download/libreoffice-fresh/ ?
Okay, did so, re-enabled the spell-checking, etc and opened the same document. Immediately I received the spinning beach ball, and Mac reported the app as unresponsive. I only waited a couple of minutes, but it seems obvious it won't recover. I will attach the crash data
Created attachment 148995 [details] Data from the crash of 6.1.5.002
Thanks for the trace and the extra information about your document. Setting back to unconfirmed
Without a test document where we can reproduce this reliably, it is going to be difficult to confirm this bug report, unfortunately.
Email me privately and I will send you a dropbox link. I don't want it generally shared, as I hope to publish it one day, but I will share it if you agree to treat it under NDA. wa4otj@yahoo.com
(In reply to wa4otj from comment #12) > Email me privately and I will send you a dropbox link. I don't want it > generally shared, as I hope to publish it one day, but I will share it if > you agree to treat it under NDA. wa4otj@yahoo.com hello, Please, send the document privately to my email ( click on my user name )
Dear wa4otj, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
I do not understand why this is in needinfo. I provided the info requested, when requested, including backtrace, and emailing the link to the document exhibiting the problem. No matter, I will provide again. I have pulled backups of the document from the original report, and have placed it on DropBox for your retrieval. I still see the problem in that version using LO Version: 6.1.5.2 Build ID: 90f8dcf33c87b3705e78202e3df5142b201bd805 Here is the DropBox link to the document again: Please do not share the link, and I will delete it soon. Please advise when you have retrieved the document. https://www.dropbox.com/s/g9t78zr0q80mtn8/Gregory%20Family%20Origins%20-%20Master%20Copy%20-%20190129.odt?dl=0 Thanks, Nathan
(In reply to wa4otj from comment #15) > ... > Here is the DropBox link to the document again: Please do not share the > link, and I will delete it soon. Please advise when you have retrieved the > document. > ... On Win10 with LO 6.3.0.4, I could open the document (540 pages). Could you upgrade to 6.2.5 or 6.3.0? Indeed 6.1 branch is EOL. If you still reproduce the crash, please apply advice from: https://wiki.documentfoundation.org/QA/FirstSteps If you use accessibility apps, please try to disable them temporarily for the test. If you still reproduce the crash, a new backtrace would be interesting to see if it still contains GrammarCheckingIterator or if it's another pb.
Opens fine for me too on Version: 6.3.0.4 Build ID: 057fc023c990d676a43019934386b85b21a9ee99 Threads CPU : 8; OS : Mac OS X 10.14.6; UI Render : par défaut; VCL: osx; Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded Mouse scrolled through entire document, stopping cursor at random points throughout leading to high CPU usage, but no crash. You might want to try Julien's suggestion of installing LO6304.
It sounds as if the problem was fixed, perhaps accidentally, in a release since January. I will upgrade and repeat the test sometime later today. Thanks, Nathan
(In reply to wa4otj from comment #18) > It sounds as if the problem was fixed, perhaps accidentally, in a release > since January. I will upgrade and repeat the test sometime later today. > > Thanks, > Nathan Let's close it as RESOLVED WORKSFORME for the time being then.
I confirm, upgrading to 6.3.0 resolves the crash. Opening the same document with the latest release does not crash. Confirm resolved. Thanks, Nathan