Description: The realease of 5.2.2.2 (but also 5.1.5.2) on macOS (10.12.0 and 10.12.1, but possibly also on 10.11.6 (I am not sure anymore)) crashes every time after a fresh installation, except for the first time starting/opening it. It does not matter whether it is being started by opening the LibreOffice application directly, or by opening a LibreOffice document, e.g. a Writer document. It is fully reproducible. And the crash produces always the same segmentation fault crash report (see attchment). However, if you open the the Java Control Panel (current version, Java 8-Update 112, but also valid for some earlier update(s)) in the macOS system preferences before starting the LibreOfiice application, it does never (!) crash and you can normally use LibreOffice as expected!!! You can now work with LibreOffice as expected, even if you close the JAVA Control Panel in the mean time. In the mean time you can for example save and reopen (Writer) documents; it works as expected. But, as soon as you restart LibreOffice without an open Java Control Panel it crashes during opening with the same results again. Again, this behavior is fully reproducible. It does also crash with LibreOffice 5.1.5.2. Exactely the same behavior. Steps to Reproduce: 1. Install release 5.2.2.2 2. Start/open application 3. work with it or not 4. close/finish it 5. Start again for the second or xth time, it crashes always with the same (reason in the) crash report (see attachment) However, if you open the the Java Control Panel (current version, Java 8-Update 112, but also valid for some earlier update(s)) in the macOS system preferences before starting the LibreOfiice application, it does never crash and you can normally use LibreOffice!!! You can now work with LibreOffice as exected, even if you close the JAVA Control Panel in the mean time. In the mean time you can save and reopen (Writer) documents; it works as expected. But, as soon as you restart LibreOffice without an open Java Control Panel it crashes during opening with the same results again. Actual Results: It crashes and OS produces a crash report (segmentation fault). Expected Results: Starting the application. Reproducible: Always User Profile Reset: No Additional Info: I am working with macOS and LibreOffice configured with German user interface. However it does not matter whether I install the LibreOffice's German language interface or not. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:49.0) Gecko/20100101 Firefox/49.0
Created attachment 128384 [details] OS crash report macOS crash report example
Created attachment 128385 [details] No crash with open Java Control Panel Screen shot with started LibreOffice with open Java Control Panel --> no crash.
@Marty : if you are using a JRE, then you need to switch to a complete JDK, see bug 101956
See also bug 94716. I suspect that this report is a dup of bug 94716
@Marty : please report back with the following information : 1) Whether or not you have Apple JavaforOSX installed 2) Whether you are just using an Oracle JRE 3) Whether or not you are just using an Oracle JDK 4) Whether or not you are using Apples's JavaforOSX along with an Oracle JRE or an Oracle JDK
Created attachment 128471 [details] verified OS crash report on a different machine I verified the exactly same behavior (crash) with the very same error (segmentation fault) on a different machine of almost the same model, but without any previous installations of either LO or Java. See attachment.
(In reply to Alex Thurgood from comment #5) > @Marty : please report back with the following information : > > > 1) Whether or not you have Apple JavaforOSX installed > 2) Whether you are just using an Oracle JRE > 3) Whether or not you are just using an Oracle JDK > 4) Whether or not you are using Apples's JavaforOSX along with an Oracle JRE > or an Oracle JDK 1) no. 2) Oracle JRE. 3) no. 4) no.
Created attachment 128472 [details] verified OS crash report on a different machine
@Marty : sorry, but you need to install an Oracle JDK instead per comment 3, this is a DUP of bug 101956 *** This bug has been marked as a duplicate of bug 101956 ***
I see. But this will be resolved later (the requirement of JDK is just a workaround)?