Description: asked to test 7.2.1 due to fault in 7.1. On launch, app crashes with error Faulting application name: soffice.bin, version: 7.2.1.2, time stamp: 0x613a5f13 Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process ID: 0x3798 Faulting application start time: 0x01d7ae6efa17d04e Faulting application path: C:\Program Files\LibreOffice\program\soffice.bin Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report ID: 75b398b9-8098-4db7-a881-7b18b4f9199c Faulting package full name: Faulting package-relative application ID: Steps to Reproduce: 1.install update 2.Launch app 3. Actual Results: app crashed with error as reported above Expected Results: didn't get to option to select which file or sub application to launch Reproducible: Always User Profile Reset: No Additional Info: cannot get far enough into app to check status of profile.
assume this issue with 7.2.1.2 is on the same system reporting bug 144282 where you list: Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 2; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL If so, with that CPU thread count this may be the SESS2 vs AVX compile issue of bug 144598 -- and you can test both issue with an install of tonights build of master [1]. Giggles and grins--what CPU and graphics GPU are you running Windows 10 (21H1) on? A run of msinfo32.exe and copy post top few items of the summary Panel, and same for the Components -> Display panel. =-ref-= [1] https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb77-TDF/current/
Created attachment 175182 [details] screen capture of msinfo dump from machine showing fault First of two pages from msinfo from machine with issue on it.
Created attachment 175183 [details] page 2 of msinfo dump Page 2 of msinfo dump, A relevant point here may be that in recent times, AMD have terminated windows support for this processor/GPU combination, and there are now supposedly no ongoing updates for this device, despite it being less than 3 years old. It makes me wonder if this is an issue that has been caused by Microsoft making changes in the latest version of Win 10 that are now breaking the drivers for the chip set. If that is the case, then I may have to take the issue up with Lenovo, as this age of machine should not have been made unsupportable at this time.
(In reply to Steve Garry from comment #3) > > A relevant point here may be that in recent times, AMD have terminated > windows support for this processor/GPU combination, and there are now > supposedly no ongoing updates for this device, despite it being less than 3 > years old. It makes me wonder if this is an issue that has been caused by > Microsoft making changes in the latest version of Win 10 that are now > breaking the drivers for the chip set. If that is the case, then I may have > to take the issue up with Lenovo, as this age of machine should not have > been made unsupportable at this time. Well, it is always annoying to have chipmaker and OEM stop supporting their HW especially such a recent system--AMD A9 CPU with R5 GPU. But for this, please check a /A admin parallel installation [1] of last nights Tinderbox build of trunk/7.3.0 --it has the patch for bug 144282 to avoid AVX calls making it in during compile and build. If install/launch is good there, should be good when added to a 7.2.2 or 7.2.3 release. =-ref-= [1] https://wiki.documentfoundation.org/Installing_in_parallel
Could you please apply this? https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28Skia.29
Skia Vulcan was indeed enabled, which may be relevant in that AMD have terminated support for the A9 processor, and are no longer providing updates, so the latest driver that this system can run is Radeon 25.5.2, and no further updates are anticipated. I have changed the setting as per the section, and Skia is no longer enabled for this device, and I will revert with an update, a very quick test would seem to be working, the application launches and I can get into the help information, which is an improvement on where things were previously. If you need any further help or testing on this hardware combination, please come back to me, as there would appear to be a potential issue as a result of AMD terminating support for a range of relatively new processor/GPU combinations.
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
If the patch to the registry mod file works, let's consider this as dup of tdf#144598. If it still fails with next LO release 7.2.2, don't hesitate to reopen this tracker. *** This bug has been marked as a duplicate of bug 144598 ***
Issues asside for your AMD A9 compute unit and R5 GPU support, the crash was a compile time issue with the LO build of 7.2.1.2. Fully disabling Skia requires manual edit of the user profile to add the stanza: <item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="UseSkia" oor:op="fuse"><value>false</value></prop></item> Please check a nightly build of trunk/7.3.0, or of 7.2.2rc1 [1] with patch for bug 144598 "protecting" our SSE2 level build, avoiding mixing AVX CPU calls. =-ref-= [1] https://downloadarchive.documentfoundation.org/libreoffice/old/7.2.2.1/win/x86_64/LibreOffice_7.2.2.1_Win_x64.msi.mirrorlist
Still seeing this issue with 7.2.2.2 on the same AMD drivers 21.5.2 (latest legacy drivers) on Windows 11. Faulting application name: soffice.bin, version: 7.2.2.2, time stamp: 0x615daec6 Faulting module name: ucrtbase.dll, version: 10.0.22000.1, time stamp: 0x00e78ce9 Exception code: 0xc0000409 Fault offset: 0x000000000007dd7e Faulting process id: 0xd2c Faulting application start time: 0x01d7bc3f09a7a21b Faulting application path: C:\Program Files\LibreOffice\program\soffice.bin Faulting module path: C:\WINDOWS\System32\ucrtbase.dll