Bug 139035 - Windows crashed after installing LibreOffice_7.0.3_Win_x64.msi
Summary: Windows crashed after installing LibreOffice_7.0.3_Win_x64.msi
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.0.3.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-18 13:09 UTC by Mike
Modified: 2020-12-19 16:06 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike 2020-12-18 13:09:10 UTC
Description:
I successfully installed 7.0.3 on my laptop the installation did NOT require a reboot of Windows.
Laptop details:
  Edition: Windows 10 Pro
  Version: 1909
  OS Build: 18363.1256
  Processor:Intel(R) Pentium(R) CPU4415U @2.30GHz
  RAM: 4GB (£.89GB available)
The laptop was purchased with the OS pre-installed.

I installed 7.0.3 on my tower PC and the installation said (on 2 occasions) that a reboot would be required. After the installation was complete the LibreOffice installer suggested rebooting so I did. All appeared fine until I started LibreOffice. When the startup logo should have appeared all that I could see was the dark line, the shadow. Then the whole screen went black (not a BSOD) and the PC restarted. After the PC had restarted I tried to run LibreOffice once more with the same result: all I could see was the dark line, the shadow. Then the whole screen went black and the PC restarted. I then downloaded the LibreOffice_7.0.3_Win_x64.msi file again (in case the first download was corrupted) and tried reinstalling but it said that a reboot would be required so I aborted the second installation attempt in case it permanently affected Windows.
I uninstalled 7.0.3 (this took a surprisingly long time: about 10 minutes) and reinstalled 6.4.7.2. This installed cleanly and runs perfectly.
PC details:
  Edition: Windows 10 Pro
  Version: 2004
  OS Build: 19041.685
  Experience: Windows Feature Experience Pack 120.2212.551.0
  Processor: AMD A10-7850K Radeon R7.12 Compute cores 4C 8G 3.70GHz
  RAM: 8GB (6.94 GB available)
The PC is older than the laptop and had Windows 7 on it for which I got the free upgrade to Windows 10 Pro. 

I hope that this helps,
Mike.

Steps to Reproduce:
1. Install 7.0.3
2. Reboot
3. Windows crashes

See a more complete description in the "Description" panel above

Actual Results:
Windows crashes

Expected Results:
Windows not crashing


Reproducible: Always


User Profile Reset: No



Additional Info:
Well, not crash my PC !!

I cannot copy the information from menu Help-About as LibreOffice crashed the PC before the startup logo appeared.
Comment 1 Xisco Faulí 2020-12-18 17:55:54 UTC
Thank you for reporting the bug.
Could you please try to reproduce it with the latest version of LibreOffice ( 7.0.4.2 ) from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 2 Julien Nabet 2020-12-18 17:57:21 UTC
Also you can try this:
https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile
Comment 3 Mike 2020-12-19 14:09:56 UTC
As Xisco Fauli suggested (comment 1) I installed LibreOffice_7.0.4_Win_x64.msi. This time the installation did not require a reboot. However the result was exactly the same: when the startup logo should have appeared all that I could see was the dark line, the shadow. Then a few seconds later the whole screen went black and the PC crashed completely; it did not restart. I pressed the power button for 4 seconds to force it to switch off and then I could restart it normally.

I the tried starting LibreOffice in Safe Mode and it worked fine, I could open .odt and .ods files.

I then followed Julien Nabet's suggestion (comment 2). I copied the whole of the C:\Users\Mike\AppData\Roaming\LibreOffice\4 directory to somewhere else for safe keeping and then deleted the C:\Users\Mike\AppData\Roaming\LibreOffice\4\user directory. Again, trying to start LibreOffice in normal mode resulted in the PC crashing.

While I was looking around C:\Users\Mike\AppData\Roaming\LibreOffice\4\crash I noticed that there was a dump.ini file which was created today and which contained:

ProductName=LibreOffice
Version=7.0.4.2
BuildID=dcf040e67528d9187c66b2379df5ea4407429775
URL=https://crashreport.libreoffice.org/submit/
UseSkia=false
OpenGLVendor=0x1002
OpenGLDevice=0x130f
OpenGLDriver=26.20.12028.2
UseOpenGL=false
Language=en-GB
ShutDown=true

In the C:\Users\Mike\AppData\Roaming\LibreOffice\4\cache directory there were two files, also created today, called:

C:\Users\Mike\AppData\Roaming\LibreOffice\4\cache\opengl_device.log
C:\Users\Mike\AppData\Roaming\LibreOffice\4\cache\skia.log

skia.log contains 0x9C(156) bytes of zeros

opengl_device.log contains:

DriverVersion: 26.20.12028.2
DriverDate: 8-16-2019
DeviceID: PCI\VEN_1002&DEV_130F&SUBSYS_01231002&REV_00
AdapterVendorID: 0x1002
AdapterDeviceID: 0x130f
AdapterSubsysID: 0x01231002
DeviceKey: System\CurrentControlSet\Control\Video\{AC31EFBC-D276-11EA-8702-D5066E76A7EB}\0000
DeviceString: AMD Radeon(TM) R7 Graphics

I hope that this helps.
Mike.
Comment 4 Julien Nabet 2020-12-19 14:25:43 UTC
I noticed your graphic driver has a version of 2019.
Is there any new version so you can upgrade?
If yes and after having upgraded, could you give a new try?

If you still reproduce this, could you attach to the bugtracker the 2 files: 
C:\Users\Mike\AppData\Roaming\LibreOffice\4\cache\opengl_device.log
C:\Users\Mike\AppData\Roaming\LibreOffice\4\cache\skia.log
?
(you can use this link:
https://bugs.documentfoundation.org/attachment.cgi?bugid=139035&action=enter)

Also, if it works in safe mode, you can launch LO in safe mode then disable hardware acceleration (menu Tools/Options/Display) and relaunch LO in normal mode
Comment 5 Mike 2020-12-19 16:00:32 UTC
Very well done Julien. Many, many thanks. The new graphics driver fixed the problem. 

Many thanks,
Mike.
P.S. May well have fixed some others too :-)
Comment 6 Julien Nabet 2020-12-19 16:06:16 UTC
(In reply to Mike from comment #5)
> Very well done Julien. Many, many thanks. The new graphics driver fixed the
> problem. 
> 
> Many thanks,
> Mike.
> P.S. May well have fixed some others too :-)

Great to hear this! :-)
Let's put this one to WFM then.