Description: I'm working on a odt document, converted from word to odt. When I'm writing some new data the program crashes continuosly. When reopen sometimes I clic on forget the recovery data and other click on recover, but it continues crashing. Steps to Reproduce: 1.open the document 2.write some paragraphs, write something wrong, delete and write again. Actual Results: The file can be downloaded from https://ufile.io/w7irgakp Expected Results: Not to crash Reproducible: Sometimes User Profile Reset: No Additional Info: Windows log says (in spanish): Nombre de la aplicación con errores: soffice.bin, versión: 7.5.1.2, marca de tiempo: 0x63f7d013 Nombre del módulo con errores: ucrtbase.dll, versión: 10.0.22621.608, marca de tiempo: 0xf5fc15a3 Código de excepción: 0xc0000409 Desplazamiento de errores: 0x000000000007f61e Identificador del proceso con errores: 0x0x6AC Hora de inicio de la aplicación con errores: 0x0x1D95DD3ED866D58 Ruta de acceso de la aplicación con errores: C:\Program Files\LibreOffice\program\soffice.bin Ruta de acceso del módulo con errores: C:\WINDOWS\System32\ucrtbase.dll Identificador del informe: 67c75d9f-5a04-4bc0-811a-b28aa3f61143 Nombre completo del paquete con errores: Identificador de aplicación relativa del paquete con errores:
Created attachment 186167 [details] file i'm working on that crash
Please test with a clean profile, Menu/Help/Restart in Safe Mode
Dear calete, 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 calete, 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
For good measure, I could not reproduce on: Version: 7.6.5.2 (X86_64) / LibreOffice Community Build ID: 38d5f62f85355c192ef5f1dd47c5c0c0c6d6598b CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Calete, if you still see this issue in 7.6 or 24.2, please let us know!