Description: The attached file worked fine in 5.1.something. I upgraded to 5.2.6.2 and now when I try to save the file, Writer faults. Steps to Reproduce: 1. Open the attached file 2. File | Save 3. boom - error with title "LibreOffice 5.2 - Fatal Error" and text "bad allocation". Actual Results: Writer faulted Expected Results: Writer no fault Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36
Created attachment 132958 [details] This file, when saved, causes Writer to fault
The error is because you run out of memory. I have 32 gigabytes of memory, so I don't get the problem. No clue, why it started doing that since 5.2.. Arch Linux 64-bit Version: 5.4.0.0.alpha1+ Build ID: aca48f46895811009ec90665d816ef835f0694be CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on 30th April 2017
I can't reproduce it in 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: grou nor Versión: 5.2.6.2 Id. de compilación: a3100ed2409ebf1c212f5048fbe377c281438fdc Subprocesos de CPU: 1; SO: Windows 6.1; Repr. de IU: predeterminado; Configuración regional: es-ES (es_ES); Calc: group To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
It in deed is a problem wich seems to be connected to the dedicated RAM. I dedicated more RAM and now it only happens with large images but still is happening on my Win10 Computer. Even if I just attached a file wich is shown properly it shows the above described fatal error as soon as I save the file. Result: file is unable to be opened again because the error shows up as soon as it tries to load the file.
the 5.2.6.2 release you reported the bug is obsolete now. please upgrade to LibO 5.3.4.2 and tell if issue persists. status NEEDINFO until then.
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 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-20180129
Dear Bug Submitter, 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-20180302