Description: Error 1/5/2023 12:50:24 PM Application Error 1000 Application Crashing Events Log Name: Application Source: Application Error Date: 1/5/2023 12:50:24 PM Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords: User: SPIN_5_RFS\Rober Computer: spin_5_rfs Description: Faulting application name: soffice.bin, version: 7.4.3.2, time stamp: 0x637706b1 Faulting module name: ucrtbase.dll, version: 10.0.22621.608, time stamp: 0xf5fc15a3 Exception code: 0xc0000409 Fault offset: 0x000000000007f61e Faulting process id: 0x0x2058 Faulting application start time: 0x0x1D9206F9869912F Faulting application path: C:\Program Files\LibreOffice\program\soffice.bin Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: 641aa7f6-efe0-4f1c-88b6-949446311c74 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2023-01-05T17:50:24.5803080Z" /> <EventRecordID>2307</EventRecordID> <Correlation /> <Execution ProcessID="10520" ThreadID="17948" /> <Channel>Application</Channel> <Computer>spin_5_rfs</Computer> <Security UserID="S-1-5-21-1415675503-1741788046-3620625906-1001" /> </System> <EventData> <Data Name="AppName">soffice.bin</Data> <Data Name="AppVersion">7.4.3.2</Data> <Data Name="AppTimeStamp">637706b1</Data> <Data Name="ModuleName">ucrtbase.dll</Data> <Data Name="ModuleVersion">10.0.22621.608</Data> <Data Name="ModuleTimeStamp">f5fc15a3</Data> <Data Name="ExceptionCode">c0000409</Data> <Data Name="FaultingOffset">000000000007f61e</Data> <Data Name="ProcessId">0x2058</Data> <Data Name="ProcessCreationTime">0x1d9206f9869912f</Data> <Data Name="AppPath">C:\Program Files\LibreOffice\program\soffice.bin</Data> <Data Name="ModulePath">C:\WINDOWS\System32\ucrtbase.dll</Data> <Data Name="IntegratorReportId">641aa7f6-efe0-4f1c-88b6-949446311c74</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event> Steps to Reproduce: Has happened randomly. Actual Results: Happens randomly. I don't know the events to reproduced it, but I've attached the event log, so maybe you will be able to figure it out. Expected Results: Happens randomly. I don't know the events to reproduced it, but I've attached the event log, so maybe you will be able to figure it out. Reproducible: Sometimes User Profile Reset: No Additional Info: Happens randomly. I don't know the events to reproduced it, but I've attached the event log, so maybe you will be able to figure it out.
Thanks for filing and sorry you're having an issue. Unfortunately not enough detail in the posted Windows event log to do anything for this issue. For starters we'd like you to copy and post the LibreOffice Help -> About details and the Windows system details from msinfo32.exe (core panel, and the components -> display panel). Also, for many "crash" scenarios LibreOffice will trigger a minidump using Breakpad and on restart offer to upload the report--are you seeing that on restart of LibreOffice? Otherwise getting more detail of your issue [1] requires you to install the WinDbg module of the Windows Development Kit and downloading the build symbols libraries. Then attaching the soffice.bin process to the debugger and capturing the moment that LibreOffice crashes on your system. Being able to isolate the part of the program causing your issues. Many of the issues with older CPU/GPU configurations like yours have been display driver related. Check for updates (from Acer or Intel). And also see if LO is stable setting Tools -> Options -> View, so both Skia rendering checkboxes are unchecked and restart. =-ref-= [1] https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Dear Bobby, 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 Bobby, 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