Description: Crash changing gradient a second time with Skia enabled (hardware mode) Steps to Reproduce: 1. Open Draw 2. Check Skia settings (Tools -> Options -> LibreOfficeDev -> View) Skia enabled, software disabled 2. Page Properties 3. Gradient tab -> Select a gradient & click OK 4. Repeat 2-3 -> Crash Could be my system; don't now if hardware variant is actually supported Actual Results: Crash Expected Results: No crash Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.0.alpha0+ (x64) Build ID: 4501a0ba623ad61c5a4e0b807da2e96f0e4ce82c CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
no repro in Версия: 7.0.0.0.alpha0+ (x64) ID сборки: 4501a0ba623ad61c5a4e0b807da2e96f0e4ce82c Потоков ЦП: 4; ОС: Windows 10.0 Build 18362; Отрисовка ИП: Skia/растр; VCL: win; Локаль: ru-RU (ru_RU); Язык интерфейса: ru-RU Calc: threaded
The given steps don't seem to work reliably. 1. Open Draw 2. Check Skia settings (Tools -> Options -> LibreOfficeDev -> View) Skia enabled, software disabled 2. Page -> Properties Gradient tab -> Select a gradient & click OK 4. Repeat 2 -> Crash -if not 5. Open Impress 6. Slide -> Properties Select a gradient & click OK 7. Repeat 6 (2 or 3 times) Note: could be related to my system. Rather old
@telesto, could you post GPU and driver details for your Windows 8.1 system Likely they will need to be blacklisted for Skia/Vulkan rendering. And just to be clear, this combination of os and GPU/driver is working with Skia/raster (the 'Force Skia software rendering')? For GPU and driver details: run msinfo32 -> components -> display tab, copy and paste the top dozen stanzas.
Force Skia software rendering is working fine (and enabled by default) Naam AMD Radeon HD 7700 Series PNP-apparaat-id PCI\VEN_1002&DEV_683D&SUBSYS_25561458&REV_00\4&12B449C0&0&0009 Adaptertype AMD Radeon Graphics Processor (0x683D), compatibel met Advanced Micro Devices, Inc. Beschrijving AMD Radeon HD 7700 Series RAM-geheugen 1,00 GB (1.073.741.824 bytes) Geïnstalleerde stuurprogramma's aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll Versie van stuurprogramma 21.19.407.0 INF-bestand oem26.inf (WB64A_ati2mtag_R575A-gedeelte)
FWIW: Also a crash when changing the tab color in calc
I cannot reproduce either. > CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: > win; That "Raster" there means that no HW acceleration is used, so your description about forced software rendering doesn't make sense.
(In reply to Luboš Luňák from comment #6) > I cannot reproduce either. > > > CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: > > win; > > That "Raster" there means that no HW acceleration is used, so your > description about forced software rendering doesn't make sense. It should be skia/vulkan. I blindly copy/paste the info. The settings are reset to Skia Force Software rendering after the crash happens. It crashes for me also when when changing the sheet tab color in Calc in combination with Skia/Vulkan. But - again - sure if my system is supported at all.
*** Bug 131578 has been marked as a duplicate of this bug. ***
Could it be this has the same root problem as bug #131696?
no repro with Skia/Vulcan Версия: 7.0.0.0.alpha0+ (x64) ID сборки: f265b14d6f8e3e63260b3c8ecce48d4251288fea Потоков ЦП: 4; ОС: Windows 10.0 Build 18363; Отрисовка ИП: Skia/Vulkan; VCL: win; Локаль: ru-RU (ru_RU); Язык интерфейса: ru-RU Calc: threaded I have here DriverVersion: 26.20.100.7325 DriverDate: 10-7-2019 DeviceID: PCI\VEN_8086&DEV_591B&SUBSYS_1A101043&REV_04 AdapterVendorID: 0x8086 AdapterDeviceID: 0x591b AdapterSubsysID: 0x1a101043 DeviceKey: System\CurrentControlSet\Control\Video\{EAD2925E-7135-11EA-9DAF-BD7266DE710B}\0000 DeviceString: Intel(R) HD Graphics 630
(In reply to Luboš Luňák from comment #9) > Could it be this has the same root problem as bug #131696? Yes, same root cause *** This bug has been marked as a duplicate of bug 131696 ***