https://bugs.documentfoundation.org/show_bug.cgi?id=158129
V Stuart Foote <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #5 from V Stuart Foote <[email protected]> --- OK, now set both stanzas to 'false' That will disable Skia rendering and fallback to GDI+ The "UseSkia" toggle does as named and defaults to Vulkan/Metal and X11/gen accelerated GPU libs, while the "ForceSkiaRaster" still uses Skia libs but with raster framing only--non-accelerated. true-false is least stable Skia but fully GPU accelerated true-true is "more" stable Skia. false-false disables Skia And setting both false forces the fallback, where your GPU will use GDI+ calls only. Win11 WDM may choke there as well. In the UI there is a "Use hardware acceleration" checkbox that will go active when the UseSkia and ForceSkiaRaster values are both set false. IIUC also disabling that checkbox pushes some 3D and some 2D rendering/anti-aliasing onto the CPU. Probably not the issue, for now just want to eliminate the Skia support as an issue with Win11 bluescreen. Also, still need the skia.log and display details. And is there a particular module of LO (i.e. draw, impress, calc) that seems to trigger issue consistently? If not a skia issue, then we'll need steps-to-reproduce. A bit of a chore to set up, but you could setup to capture a backtrace (Win11 SDK with symbols from LO [1]) which may show events from LibreOffice before the os BlueScreen. =-ref-= [1] https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg -- You are receiving this mail because: You are the assignee for the bug.
