Bug 136556 - LO 7.0, 6.4, 6.2 all crash when trying to save or `save as' a document or spreadsheet
Summary: LO 7.0, 6.4, 6.2 all crash when trying to save or `save as' a document or spr...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-07 16:54 UTC by Glyn Weston
Modified: 2020-09-29 14:57 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: crashreport.libreoffice.org/stats/crash_details/7b97ed38-112c-4f10-b9cc-7da6572391a7

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Glyn Weston 2020-09-07 16:54:47 UTC 
Description:
After upgrading to LO 7.0.0.3 on trying to "save" or "save as" a document or spreadsheet the program crashes. It leaves a small Document Recovery window which is totally unresponsive to the mouse or Alt F4. It requires Win Task Manager to end the process. This happen both in normal and safe modes.

Steps to Reproduce:
1.Mouse left click "File"
2.Mouse left click "Save" or "Save As"
3.Program immediately crashes leaving an unresponsive Document recovery window.

Actual Results:
After using Task Manager to remove the unresponsive Document recovery window LO has shut down completely. It did not get as far as choosing a file name.

Expected Results:
It should have displayed a file name selection window.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 7.0.1.2 (x64)
Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Vulkan; VCL: win
Locale: en-GB (en_GB); UI: en-US
Calc: CL
Comment 1 Glyn Weston 2020-09-13 23:34:37 UTC 
As I suspected the problem lay with one of the Win 10 updates and although Chkdsk C: could find no errors The System File Checker Utility (SFC) found errors as did the DISM Scan (Deployment Image Servicing and Management) which could not be repaired. 
Rather than go for a Windows recovery I tried the Win 10 feature update to Ver 2004 which after it had finished cured the problem, presumably overwriting whichever dll was corrupt..It also cured a problem with the Microsoft Management Console which prevented me accessing Disk