Description: I'm not sure how it happens, but after about a few minutes or fewer, LibreOffice just closes itself for no reason. This is after I had copied the text of another file (that has 4,838 words and 28,049 characters on it, and has about 68 pages) onto a new LibreOffice Writer file and did some work on it. It is really annoying and I hope that this gets fixed as soon as possible. Steps to Reproduce: 1. Open up a file using LibreOffice 2. Copy it onto a new Writer file 3. Wait for a few minutes as you work on it Actual Results: Haven't tried purposefully replicating it yet. Expected Results: As I said above, Writer should crash and close the file that's being worked on. Reproducible: Didn't try User Profile Reset: No Additional Info: I honestly don't know what to put here, so I'll just say this; good luck trying to fix this bug.
An update to this, turns out it just automatically crashes after a couple minutes regardless of the steps I listed on how to replicate it. Still stupid that this is a thing, like recently I practically BEGGED for it to not crash, and it still crashed anyways.
Could you try this https://wiki.documentfoundation.org/QA/FirstSteps ?
Happens also with 7.6 release. The head of the crash report (may reported fully if someone would volonteer to read it ;-) : ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: soffice [26739] Path: /Applications/LibreOffice.app/Contents/MacOS/soffice Identifier: org.libreoffice.script Version: 7.6.0.3 (7.6.0.3) Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 502 Date/Time: 2023-09-02 09:19:13.6479 +0200 OS Version: macOS 12.6.8 (21G725) Report Version: 12 Anonymous UUID: 03032271-9E71-FDD0-7095-862B5FA65C77 Sleep/Wake UUID: 2282A79D-FA16-4672-B6B1-D75753A1C0E1 Time Awake Since Boot: 130000 seconds Time Since Wake: 2402 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_INSTRUCTION (SIGABRT) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
sorry, forget to mention: It happened repeatedly after LO was idling some time
(In reply to Uwe Altmann from comment #3) > Happens also with 7.6 release. > The head of the crash report (may reported fully if someone would volonteer > to read it ;-) : >... There's no backtrace here. You can follow https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#macOS:_How_to_get_debug_information to get it one.
Let's put this one to NEEDINFO following comment 2.
Okay so turns out, it was crashing because of anti-aliasing being on. After I turned it off, it seems to have stopped crashing. Still feel like this is something that should be fixed if I'm being honest.
Created attachment 189318 [details] full crash report full crash report
(In reply to Uwe Altmann from comment #8) > Created attachment 189318 [details] > full crash report > > full crash report I would have expected a better readibility (like https://bug-attachments.documentfoundation.org/attachment.cgi?id=189319). Hope someone may find something in your crash log.
(In reply to ca.wright626 from comment #7) > Okay so turns out, it was crashing because of anti-aliasing being on. After > I turned it off, it seems to have stopped crashing. Still feel like this is > something that should be fixed if I'm being honest. On which env are you? Did you install any specific fonts? (since antialiasing may be related with fonts) Did you follow https://wiki.documentfoundation.org/QA/FirstSteps ? Would it be possible you retrieve a backtrace? (by following https://wiki.documentfoundation.org/QA/BugReport/Debug_Information)
(In reply to Uwe Altmann from comment #8) > Created attachment 189318 [details] > full crash report > > full crash report If you disable antialiasing, do you reproduce this? If yes, it means it's another pb and you should submit a new bugtracker.
(In reply to Julien Nabet from comment #11) > (In reply to Uwe Altmann from comment #8) > > Created attachment 189318 [details] > > full crash report > > > > full crash report > > If you disable antialiasing, do you reproduce this? > If yes, it means it's another pb and you should submit a new bugtracker. I did - we'll see.........
Dear ca.wright626, 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
Dear ca.wright626, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA 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 MassPing-NeedInfo-FollowUp