Description: 5.3 versions crash immediately upon opening a LibreOffice writer file. 5.1.2 doesn't crash. Here's the file (I don't see any other way to send it to you, despite all the long questionnaire) http://www.media.mit.edu/~lieber/Misc/Bug-Reports/jailbreaking_the_prisoners_dilemma.odt Error message: http://web.media.mit.edu/~lieber/Misc/Bug-Reports/LO-Error-Message-20-Apr-17.jpeg I'm also still having trouble with the 5.1 versions on editing .odm files. (This file above is a chapter in a book). Will crash on trying to save or print an .odm. Or it'll save OK but the next time it'll make me go through the recovery dialog. Here's the .odm: http://web.media.mit.edu/~lieber/Misc/Bug-Reports/LO-Error-Message-20-Apr-17.jpeg Steps to Reproduce: 1. Load file mentioned. 2. 3. Actual Results: Crash. Expected Results: I should be able to edit the file without LO crashing. Reproducible: Always User Profile Reset: Tried it once, to no avail. Not unique to one version. Additional Info: This questionnaire is way too long for a bug report, too much work for users. I'm willing to help if you interact with me, but this is too much upfront work for a bug report. Bug reports need a way to send you the files in question. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
Created attachment 132718 [details] File causing LO 5.3.2 to crash
Created attachment 132719 [details] .odm file for book of which "Jailbreaking..." file is a chapter
I can't reproduce it in Version: 5.3.2.2 Build ID: 1:5.3.2~rc2-0ubuntu1~yakkety0 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Layout Engine: new; Locale: es-ES (ca_ES.UTF-8); Calc: group or Versión: 5.3.2.2 Id. de compilación: 6cd4f1ef626f15116896b1d8e1398b56da0d0ee1 Subproc. CPU: 1; SO: Windows 6.1; Repr. de IU: predet.; Motor de trazado: HarfBuzz; Configuración regional: es-ES (es_ES); Calc: group
No crash here. Henry: could you please copy and paste the text from "LibreOffice - About LibreOffice" menu? Version: 5.3.2.2 Build ID: 6cd4f1ef626f15116896b1d8e1398b56da0d0ee1 CPU Threads: 4; OS Version: Mac OS X 10.12.4; UI Render: default; Layout Engine: new; Locale: en-US (en_FI.UTF-8); Calc: group
On pc Debian x86-64 with master sources updated 2 days ago, I don't reproduce the crash but noticed these logs on console: warn:legacy.osl:6673:1:xmloff/source/draw/ximpshap.cxx:3825: DBG_UNHANDLED_EXCEPTION in virtual void SdXMLCustomShapeContext::EndElement() when: flushing after load type: com.sun.star.beans.UnknownPropertyException message: FlushCustomShapeUnoApiObjects context: 14SvxCustomShape warn:legacy.osl:6673:1:xmloff/source/draw/ximpshap.cxx:3825: DBG_UNHANDLED_EXCEPTION in virtual void SdXMLCustomShapeContext::EndElement() when: flushing after load type: com.sun.star.beans.UnknownPropertyException message: FlushCustomShapeUnoApiObjects context: 14SvxCustomShape warn:legacy.osl:6673:1:xmloff/source/draw/ximpshap.cxx:3825: DBG_UNHANDLED_EXCEPTION in virtual void SdXMLCustomShapeContext::EndElement() when: flushing after load type: com.sun.star.beans.UnknownPropertyException message: FlushCustomShapeUnoApiObjects context: 14SvxCustomShape
No repro Version: 5.3.2.2 Build ID: 6cd4f1ef626f15116896b1d8e1398b56da0d0ee1 Threads CPU : 2; Version de l'OS :Mac OS X 10.12.4; UI Render : par défaut; Moteur de mise en page : nouveau; Locale : fr-FR (fr_FR.UTF-8); Calc: group
@Henry : please file a separate report for the master document issue. As 5.1 is quite old, it has probably already been reported, and possibly fixed.
Henry is using OSX 10.10.5 - there are already reports of various crashes using current versions of LO with older versions of OSX, in particular 10.10
Henry: Just out of interest, are you using OS X 10.10 because of sentimental reasons ("it's the last good one", or sumesuch), or because you have hardware that can't be updated to a current macOS?
I am using Mac OS 10.10 on a 2013 vintage Mac. I plan on getting a new Mac soon so I am reluctant to update the OS, upgrades not always being pain-free. I realize it may be an OS issue, not necessarily LO, if you can't reproduce it. But this happening consistently with LO. Anything I can do to help track it down?
@Henry: if you start LO from the terminal with : /Applications/LibreOffice.app/Contents/MacOS/soffice and load the document: 1) does it still crash ? 2) is there any output to the terminal if it crashes ? 3) if there is output to the terminal when it crashes, can you post it as a text attachment to this bug ? Thanks.
Created attachment 133579 [details] Terminal output and crash report
Created attachment 133580 [details] Terminal output and crash report, file attached
So, from the crash trace, it would appear that : 17 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 41 (CoreFoundation + 527481) [0x7fff8711bc79] 1-17 17 mshMIGPerform + 199 (HIServices + 28953) [0x7fff8edf6119] 1-17 17 _XCopyAttributeNames + 385 (HIServices + 176342) [0x7fff8ee1a0d6] 1-17 17 _AXXMIGCopyAttributeNames + 252 (HIServices + 142302) [0x7fff8ee11bde] 1-17 17 CopyAttributeNames + 262 (AppKit + 4666728) [0x7fff84eee568] 1-17 17 _CFAutoreleasePoolPop + 50 (CoreFoundation + 239346) [0x7fff870d56f2] 1-17 17 malloc_zone_malloc + 71 (libsystem_malloc.dylib + 9831) [0x7fff8fe64667] 1-17 17 _sigtramp + 26 (libsystem_platform.dylib + 20250) [0x7fff8e5a3f1a] 1-17 is the root cause. From what I have seen in similar reports with Scribus and Delibar, this seems to be linked to cairo support. No idea which dev might have an inkling about what is going on here.
@Henry: do you have the Assistive Technology option activated on your Mac ? In other words, anything like VoiceOver, or another screen reader, or screen magnifier, or any assistive technology device ?
@Henry: are you using MacSpeech Dictate ?
See the linked bug reports under "See Also", where the same code path is executed. From similar trace reports in other OSX software, the "objc_send" and "semaphore" messages might imply that a pointer or a reference has been deallocated from memory, but that an attempt is then made to address it by the main loop, which would implicate VCL lifecycle management.
I don't have MacSpeech Dictate on. I do use Dragon speech dictation. I do have the Accessibility turned on for Quickeys, and for a screen recorded IShowU Instant. Henry
(In reply to Henry Lieberman from comment #18) > I don't have MacSpeech Dictate on. I do use Dragon speech dictation. I do > have the Accessibility turned on for Quickeys, and for a screen recorded > IShowU Instant. > If you turn off the Accessibility functions completely, does LO still crash when opening a Writer file ?
(In reply to Henry Lieberman from comment #18) > I don't have MacSpeech Dictate on. I do use Dragon speech dictation. I do > have the Accessibility turned on for Quickeys, and for a screen recorded > IShowU Instant. > @Henry : Dragon speech dictation is known to cause LO to crash - see bug 80756 Marking this report as DUPLICATE of that one. *** This bug has been marked as a duplicate of bug 80756 ***