Description: Sorry, LibreOfficeWriter from master~2021-09-01_02.56.07_LibreOfficeDev_7.3.0.0.alpha0_Linux_x86-64_deb.tar.gz crashed over and over when dealing with large LO Writer documents (>=500 pages). After this trial, I also tried it with versions a few days before 2021-09-01: They all crashed when I used them with large LO Writer documents. The crashes happen under Xubnutu 18.04 (which is not an actual version, I know. I did not have a chance to test it on Ubuntu 20.04). The crash error message was "Bitte prüfen Sie den Bericht und, falls bisher kein Fehler mit diesem Absturz verknüpft ist, eröffnen Sie einen neuen Fehlerbericht auf bugs.documentfoundation.org. Fügen Sie eine detaillierte Beschreibung hinzu, wie der Absturz reproduziert werden kann, und geben Sie die angezeigte Crash-ID im Feld Crash-Report ein. Vielen Dank für Ihre Unterstützung beim Verbessern von LibreOfficeDev." I did not find any crash ID. I followed the guideline https://help.ubuntu.com/community/ReportingBugs#Reporting_a_crash. Whoopsie is present. /etc/gdm3/custom.conf does not exist: the whole directory /etc/gdm3 is absent. /etc/default/apport has a line enabled=0. I found a comment of myself next to it that I have canged it to "0" in December 2019 because there were crashes with xorg happening again and again at that time. I just it back to "enabled 1". There is no file in /var/crash. Now I installed Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 491678690b5b40f446b40c368ec4b4423ee603c1 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-09-07_18:32:17 Calc: threaded and I encountered a similar crash (also without the least hint what went wrong there). Nevertheless, it looks like this crashing behavior has become a bit better than before, since I experienced the bug just once. I found this in /var/lib/whoopsie/whoopsie-id (file of today, probably this one happened with the version of 2021-09-01 before the installation of the more recent version, so this one does not describe the crash happening with that one and neither with the most recent one): 73ce1551f84baa8785ffca91b4bd48240f8ea9c911c8ac157972b23210f44bf5e9b55305c1361d74355529bc1788ec5a3955bd5443ef925fa194a978e752efbb Steps to Reproduce: 1.Start LO Writer with a large file 2. 3. Actual Results: Crash, offering to reconstruct the file which resulted in another crash. The affected files could be processed further with Version: 6.4.4.2 Build-ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff CPU-Threads: 4; BS: Linux 5.4; UI-Render: Standard; VCL: gtk3; Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: threaded Expected Results: No crash Reproducible: Always User Profile Reset: No Additional Info: The bug happened very soon when applying some edits to large existing documents. On the next restart, LO Writer offered to reconstruct them but when doing so, it crashed again, so it became an endless loop.
Adalbert, please attach your example file with >=500 pages here
Dear Adalbert Hanßen, 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
Roman, the bug happened first immediately after I upgraded LibreOffice to an actual development version. I could not attach the >=500 pages document for privacy reasons. Of course my main concern at that point was to reconstruct my current work in that file. Unfortunately I have no notes how I really achieved this, probably it was from a stored intermediate version which I make from time to time for growing really big documents like this one. I know that I tried to create a smaller anonymous version of the big file by one, in which all lower case letters are turned to “a”, all upper case letters to “A” and all digits to “0”. But he difficulty was, that I used LibreOffice itself for that purpose and I could not apply any changes to the faulty document. Unfortunately I did not store the faulty file so I can’t try to make a change like the one envisaged by other means. I kept an open eye on this type of bug but never encountered one more. Sorry. Let’s close his issue.
Ok, let's close it now as INVALID, but please feel free to reopen it if you'll catch the problem