Bug 148574 - LibreOffice Writer instant crash upon opening or creating a (new) document
Summary: LibreOffice Writer instant crash upon opening or creating a (new) document
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-04-13 15:56 UTC by mbstein
Modified: 2023-02-28 03:20 UTC (History)
6 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 mbstein 2022-04-13 15:56:40 UTC
I just installed LibreOffice on my Windows 10 Pro system. And it instantly crashes if I open a Writer-associated file or create a new document in it.

Can't find out why though.

Steps to Reproduce:
1. Open LibreOffice Writer with an automatic creation of a 'new document', or attempt to open an associated file

Actual Results:
LibreOffice crashes almost straightaway

Expected Results:
Not crash

Reproducible: Always

User Profile Reset: Yes

OpenGL enabled: Yes

Additional Info:
Version: (x64) / LibreOffice Community
Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0
CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 1 mbstein 2022-04-13 15:59:05 UTC
In save mode it doesn't crash for some reason. Again, not sure why
Comment 2 Roman Kuznetsov 2022-04-13 20:12:03 UTC Comment hidden (obsolete)
Comment 3 mbstein 2022-04-13 20:14:39 UTC
(In reply to Roman Kuznetsov from comment #2)
> Could you please try reset your LibreOffice's user profile using
> Help->Restart in safe mode dialog? And then try retest your problem

That was one of the things I attempted before I submitted this bug report. As I already toggled 

>User Profile Reset: Yes
Comment 4 Roman Kuznetsov 2022-04-13 20:43:22 UTC Comment hidden (obsolete)
Comment 5 mbstein 2022-04-13 20:45:38 UTC
(In reply to Roman Kuznetsov from comment #4)
> Ok, next question: could you please disable Skia rendering in Options dialog
> an try retest the problem? (menu Tools->Options, then LibreOffice->View
> inside the dialog, then uncheck the Skia option)

That seems to do the trick.
Comment 6 Roman Kuznetsov 2022-04-13 21:12:08 UTC Comment hidden (obsolete)
Comment 7 mbstein 2022-04-13 21:17:30 UTC
(In reply to Roman Kuznetsov from comment #6)
> (In reply to mbstein from comment #5)
> > That seems to do the trick.
> Please find a
> C:\Users\<User_name>\AppData\Roaming\LibreOffice\4\cache\opencl_devices.log
> and skia.log files and write here what its both contain. 
> (We need info about your videocard)


>Device Index: 0  
>Selected: true  
>Device Name: gfx1032  
>Device Vendor: Advanced Micro Devices, Inc.  
>Device Version: OpenCL 2.0 AMD-APP (3302.6)  
>Driver Version: 3302.6 (PAL,LC)  
>Device Type: gpu  
>Device Extensions: cl_khr_fp64 cl_khr_global_int32_base_atomics >cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics >cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics >cl_khr_int64_extended_atomics cl_khr_3d_image_writes >cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing >cl_khr_gl_depth_images cl_amd_device_attribute_query cl_amd_media_ops >cl_amd_media_ops2 cl_khr_d3d10_sharing cl_khr_d3d11_sharing >cl_khr_dx9_media_sharing cl_khr_image2d_from_buffer cl_khr_subgroups >cl_khr_gl_event cl_khr_depth_images cl_khr_mipmap_image >cl_khr_mipmap_image_writes cl_amd_liquid_flash cl_amd_copy_buffer_p2p >cl_amd_planar_yuv
>Device OpenCL C Version: OpenCL C 2.0 
>Device Available: true
>Device Compiler Available: true
>Device Linker Available: true
>Platform Name: AMD Accelerated Parallel Processing
>Platform Vendor: Advanced Micro Devices, Inc.
>Platform Version: OpenCL 2.1 AMD-APP (3302.6)
>Platform Profile: FULL_PROFILE
>Platform Extensions: cl_khr_icd cl_khr_d3d10_sharing cl_khr_d3d11_sharing >cl_khr_dx9_media_sharing cl_amd_event_callback cl_amd_offline_devices 


>RenderMethod: vulkan
>Vendor: 0x1002
>Device: 0x73ff
>API: 1.2.188
>Driver: 2.0.198
>DeviceType: discrete
>DeviceName: AMD Radeon RX 6600 XT
>Denylisted: no
Comment 8 Roman Kuznetsov 2022-04-13 21:33:39 UTC
Thank you. I can't confirm it myself because I don't have the same device.
But it seems Skia related.

Tip for you - try use Force software Skia rendering option in the same Option dialog or just disable Skia at all while developers fix this problem
Comment 9 Telesto 2022-04-16 17:54:36 UTC
You could try to update your videocard driver..
Comment 10 Julien Nabet 2022-04-16 18:33:05 UTC
Here extra info about Skia pbs:
Comment 11 Timur 2022-05-09 11:03:52 UTC
Please test with daily master Win-x86_64@tb77-TDF from https://dev-builds.libreoffice.org/daily/master/current.html to confirm if the bug is gone with bug 146402.
Comment 12 Timur 2022-05-09 11:13:33 UTC
Or a duplicate of bug 145803?
Comment 13 QA Administrators 2023-01-28 03:25:25 UTC Comment hidden (obsolete)
Comment 14 QA Administrators 2023-02-28 03:19:59 UTC
Dear mbstein,

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