https://bugs.documentfoundation.org/show_bug.cgi?id=152894
V Stuart Foote <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC| |[email protected] Summary|Below please find the event |random crashes in Writer |log in connection with a |(Windows) |crash of Writer. I think | |this has happened several | |times since I recently | |started using this | |computer, an Acer Spin 5 | |with an I-5 8th gen | |processor | --- Comment #1 from V Stuart Foote <[email protected]> --- 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 -- You are receiving this mail because: You are the assignee for the bug.
