Created attachment 115009 [details] crash report LibreOffice 4.4.2 on MacOS 10.9.5 crashes by exiting.
@Benjamin : doing what ? Please provide us with detailed information as to what you were doing, or attemmpting to do, when LibreOffice crashed, otherwise we can not move this report further, and it will be closed as invalid. Please specify : 1) Reproducible steps to invoke the crash 2) your Java version(s), if installed 3) if the crash happens with a particular document, upload a copy of the file to the report (Add an attachment). Setting to NEEDINFO pending requested information. Pleass set back to UNCONFIRMED once this information has been provided.
Please also indicate whether you are running any Accessibility tools, i.e. VoiceOver, Assistive technologies, or other utilities, like Screen Readers, etc
> 1) Reproducible steps to invoke the crash LibreOffice crashed a few times while closing the program. Does not happen every time, therefore not reproducible. > 2) your Java version(s), if installed Java 8.40 > 3) if the crash happens with a particular document, upload a copy of the file to the report (Add an attachment). Crash happened with and without open documents. No further voicover or similar tools active / in use.
So it is not reproducible with a precise set of circumstances, we can't confirm - setting back to UNCONFIRMED
The attached backtrace looks like it has something to do with a BASIC script. Do you regularly use a document or documents with internal scripts, or run a system-wide script on documents? If you get any more such crashes, please attach them so we can compare and determine if you are experiencing one issue or several. (Reports from past crashes may still be available in the directory ~/Library/Logs/DiagnosticReports/ . You may need to unhide your Library folder to access them - see http://www.macworld.com/article/2057221/how-to-view-the-library-folder-in-mavericks.html . The crash logs which are of interest here have filenames beginning with "soffice_") Setting Status -> NEEDINFO. Please return it to UNCONFIRMED when the requested information has been provided. Thanks
Created attachment 115342 [details] crash report 2015-04-16
Created attachment 115343 [details] crash report 2015-04-17
Created attachment 115344 [details] crash report 2015-04-18 1
Created attachment 115345 [details] crash report 2015-04-18 2
Created attachment 115346 [details] crash report 2015-04-19
Created attachment 115347 [details] crash report 2015-04-21 1
Created attachment 115348 [details] crash report 2015-04-21 2
Created attachment 115349 [details] crash report 2015-04-28
Created attachment 115350 [details] crash report 2015-04-29 1
Created attachment 115351 [details] crash report 2015-04-29 2
Created attachment 115352 [details] crash report 2015-04-29 3
Created attachment 115353 [details] crash report 2015-04-29 4
Created attachment 115354 [details] crash report 2015-04-29 5
Created attachment 115355 [details] crash report 2015-04-30
@Benjamin : which extensions, if any, do you have installed within LO ?
Created attachment 115356 [details] crash report 2015-05-04
Created attachment 115357 [details] crash report 2015-05-05 1
Created attachment 115358 [details] crash report 2015-05-05 2
Created attachment 115359 [details] crash report 2015-05-05 3
Created attachment 115360 [details] crash report 2015-04-15
oh, in this directory I found some more crash logs like our first one. I hope these will help.
Thanks for the additional information. So, from these additional crashes we can see that it appears to be the same issue each time. We're still missing a way to reproduce the issue though - any more help you could give with that would be appreciated. To repeat my other earlier question, - Do the document(s) you have issues with contain any BASIC scripts, or do you use any global scripts on them? And, as also mentioned by @Alex Thurgood, - Have you installed any extensions? (which can also contain BASIC)
Seems to me that this is a DUP of bug 90969 - same trace ?
Dear Bug Submitter, 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 INVALID 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
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team This INVALID Message was generated on: 2016-05-09