Bug 150178 - LibreOffice Writer crashes when opening an ODT file if hardware acceleration is enabled on Windows 11 Pro
Summary: LibreOffice Writer crashes when opening an ODT file if hardware acceleration ...
Status: RESOLVED DUPLICATE of bug 150111
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Skia
  Show dependency treegraph
Reported: 2022-07-28 05:17 UTC by Bobby Moss
Modified: 2022-08-10 14:57 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Bobby Moss 2022-07-28 05:17:41 UTC
As it says in the title, every time I try to open the latest version of LibreOffice on my gaming PC, the program crashes as soon as I try to create or load an ODT file.

Desktop PC hardware specs:
AMD Ryzen 7 3700X CPU
AMD Radeon RX 6700 XT

The operating system is Windows 11 Pro 21H2 22000.795. My Acer monitor is running at 1440p resolution with normal scaling. HDR and Night Light are not switched on.

I resolved the problem by switching off graphics hardware acceleration through LibreOffice Safe Mode. Just clearing user profile and resetting plugins did not help.

Steps to Reproduce:
1. Install LibreOffice
2. Open or Create a file in Writer

Actual Results:
Writer crashes after the automatic tip window appears.

Expected Results:
Writer should have allowed me to dismiss the tip window and continue as normal.

Reproducible: Always

User Profile Reset: Yes

OpenGL enabled: Yes

Additional Info:
Version: (x64) / LibreOffice Community
Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01
CPU threads: 16; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win
Locale: en-GB (en_GB); UI: en-US
Calc: threaded

I also found this repeated error message in the Windows event viewer:
Faulting application name: soffice.bin, version:, time stamp: 0x62d2d25a
Faulting module name: ucrtbase.dll, version: 10.0.22000.1, time stamp: 0x00e78ce9
Exception code: 0xc0000409
Fault offset: 0x000000000007dd7e
Faulting process id: 0x1df0
Faulting application start time: 0x01d8a178f2f78981
Faulting application path: C:\Program Files\LibreOffice\program\soffice.bin
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: a4f013b0-e834-440b-86a1-526cc7642085
Faulting package full name: 
Faulting package-relative application ID:
Comment 1 Bobby Moss 2022-07-28 05:34:10 UTC
Also graphics card to monitor connection is via DisplayPort. I don't think that affects anything, but just adding it in case it helps with the troubleshooting process.

My googling for the DLL in Windows Event Viewer makes me think there might be something about the Visual C++ redistributable package that's breaking things, but I don't know enough about the LibreOffice codebase or packaging to diagnose that.
Comment 2 Julien Nabet 2022-07-28 07:37:35 UTC
Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps ?
Comment 3 Bobby Moss 2022-07-28 07:59:57 UTC
Will do some time this evening UK time. :)

I think I know where you're going with this. I'll try with and without Skia enabled, as I'm guessing that Safe Mode set that to "forced" to resolve my crashing problems. Will confirm if that's the case or not and pass along the log.
Comment 4 Julien Nabet 2022-07-28 08:03:35 UTC
Indeed, have in mind to check you got last graphic driver first.
However, I'm not sure but I think we got some pb when using Skia on Windows 11.
Comment 5 Bobby Moss 2022-07-29 06:56:05 UTC
So in my own testing:

* No crashing if Skia is disabled entirely
* No crashing if Skia is enabled with forced software rendering

The application does crash though is Skia is enabled and I'm *not* forcing software rendering.

Contents of <userprofile>/cache/skia.log when it's on and forcing software rendering:

Skia on & forced rendering:
RenderMethod: raster
Compiler: Clang

Skia on with no forced rendering:
RenderMethod: vulkan
Vendor: 0x1002
Device: 0x73df
API: 1.2.188
Driver: 2.0.198
DeviceType: discrete
DeviceName: AMD Radeon RX 6700 XT
Denylisted: no

Crash dump when Skia is enabled but not forcing software rendering:
VulkanDeviceName=AMD Radeon RX 6700 XT
CPUModelName=AMD Ryzen 7 3700X 8-Core Processor             
CPUFlags=sse3 pclmulqdq monitor ssse3 fma cpmxch16b sse41 sse42 movbe popcnt aes xsave osxsave avx f16c rdrand msr cx8 sep cmov clfsh mmx fxsr sse sse2 ht fsgsbase bmi1 avx2 bmi2 rdseed adx sha lahf abm sse4a syscall mmxext rdtscp
MemoryTotal=16729512 kB
Comment 6 Julien Nabet 2022-07-29 07:00:31 UTC
Thank you for the feedback!

Luboš: since it's Skia related, thought you might be interested in this one.
Comment 7 Bobby Moss 2022-07-29 07:02:03 UTC
Also if it helps, Windows Update claims I already have the latest driver installed for my AMD RX 6700 XT graphics card. (Driver provider AMD, Driver version 30.0.13023.4001, Driver date 2021-12-16, Driver signer is Microsoft)
Comment 8 Timur 2022-08-10 14:57:27 UTC
Seem duplicate. Better to have a single conformed bug than 2 unconfirmed.

*** This bug has been marked as a duplicate of bug 150111 ***