[Libreoffice-bugs] [Bug 144630] 7.2.1 is crashing on launch.

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Sat Sep 25 13:06:46 UTC 2021


https://bugs.documentfoundation.org/show_bug.cgi?id=144630

--- Comment #7 from Steve Garry <info at huntsgrove.ie> ---
Further update, the issue with the crash on startup would appear to be profile
related, in that the earlier test was carried out using a new profile. On
restoring the old profile, it is once again impossible to start the
application, it crashes with the same ucrt error. I have checked using safe
mode to see what is stored regarding skia, and tested the option to disable all
acceleration, but it still does not start in normal mode. 

I have checked, in safe mode, and ensured that SKIA is NOT enabled, then tried
a restart in normal mode, but the app is not loading. 

Skia Log is showing
enderMethod: vulkan
Vendor: 0x1002
Device: 0x98e4
API: 1.2.170
Driver: 2.0.179
DeviceType: integrated
DeviceName: AMD Radeon(TM) R5 Graphics
Denylisted: no


OpenCL devices log 
Device Index: 0
  Selected: true
  Device Name: Stoney
  Device Vendor: Advanced Micro Devices, Inc.
  Device Version: OpenCL 2.0 AMD-APP (3240.6)
  Driver Version: 3240.6
  Device Type: gpu 
  Device Extensions: cl_khr_fp64 cl_amd_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_vec3 cl_amd_printf
cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_d3d10_sharing
cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_khr_image2d_from_buffer
cl_khr_spir 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_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 (3240.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 


Dump.ini file from startup

ProductName=LibreOffice
Version=7.2.1.2
BuildID=87b77fad49947c1441b67c559c339af8f3517e22
URL=https://crashreport.libreoffice.org/submit/
UseSkia=false
Language=en-GB
CPUModelName=AMD A9-9425 RADEON R5, 5 COMPUTE CORES 2C+3G   
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 lahf abm sse4a xop tbm syscall mmxext rdtscp
MemoryTotal=7225320 kB
ShutDown=true


I am completely confused by this now, with my user profile renamed, so creating
a new profile, it still crashes, but it is by default enabling SKIA. I have
tried disabling SKIA in safe mode, then restarting, but it still crashes, with
the same crash as originally reported. 

Skia Log from failed start with new profile, 

RenderMethod: vulkan
Vendor: 0x1002
Device: 0x98e4
API: 1.2.170
Driver: 2.0.179
DeviceType: integrated
DeviceName: AMD Radeon(TM) R5 Graphics
Denylisted: no


So, with new profile, and supposedly setting SKIA off in safe mode, it still
crashes. I have applied patch to the registry mod file as suggested, and it now
loads, and the skia log is 

RenderMethod: vulkan
Vendor: 0x1002
Device: 0x98e4
API: 1.2.170
Driver: 2.0.179
DeviceType: integrated
DeviceName: AMD Radeon(TM) R5 Graphics
Denylisted: no


Not sure how to proceed now, clearly there is something strange happening,
hopefully the people closer to the application may have an idea

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20210925/7b030fc1/attachment-0001.htm>


More information about the Libreoffice-bugs mailing list