https://bugs.documentfoundation.org/show_bug.cgi?id=129062
--- Comment #8 from V Stuart Foote <[email protected]> --- (In reply to R. Grafe from comment #7) > LO is under Windows 11 unusable for me and many others. Works fine under > Linux, but not under Windows. > ... > That was also my experience. I disabled Skia and then it works. > Incomprehensible! Absolutely false FUD! That bug 166932 was an issue with specific formatted document when opened with GDI+ rendering that exhausted GDI object handles. To resolve, filtering for the Style objects was changed. It had nothing to do with skia libs (Vulkan or fall back CPU raster rendering) which at that point was an alternative rendering mode. At the 26.2 release, the deprecated GDI+ rendering paths were removed [1]. This was necessary for feature implementation of correct alpha channel color rendering that neither GDI+ on Windows, nor aqua on macOS could process. So it is legacy GDI+ rendering that is no longer present, but few users were actually using legacy GDI+ rendering paths with skia lib based rendering set disabled. Simply at this point skia graphics libs can not be fully "disabled", and activating legacy GDI+ rendering paths, they've been removed from source. Skia Vulkan/Metal accelerated hw rendering has been set enabled by default since implemented in 2020 at the 7.0 release (replacing Cairo lib tooling with skia lib), and *Vulkan is what causes* the LibreOffice issue for folks with marginal hardware and driver configurations. But, as with prior OpenGL hw accelerated rendering, the skia lib based Vulkan hw acceleration can be toggled enabled or disabled. Done by user action (from UI or in config file), or LibreOffice graphics test, or by deny list processing. LibreOffice implements graphics functional testing on startup, and a deny listing registry, to force marginal systems fallback to skia CPU software rendering. The "fallback" skia lib based CPU software rendered raster framing is much less sensitive to poorly supported GPU or outdated graphics drivers, and that keeps those systems functional. Users can force skia CPU software rendering via the expert config stanza 'ForceSkiaRaster' set "true". Alternatively they can add the stanza in their per user LibreOffice profile "registrymodifications.xcu". A simple copy and paste of this stanza to the bottom of the .xcu will suffice: <item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="ForceSkiaRaster" oor:op="fuse"><value>true</value></prop></item> The project has discussed setting the skia lib default rendering mode to non-accelerated CPU rendering; but consensus remains that keeping Vulkan hw accelerated rendering as default is more beneficial (it keeps the rendering most performant, and fosters the deny list process). Folks experiencing issues with LO start-up or specific UI rendering issues remain encouraged to submit well described BZ issues. =-ref-= [1] See https://gerrit.libreoffice.org/c/core/+/186250 (macOS) or https://gerrit.libreoffice.org/c/core/+/187176 (win) -- You are receiving this mail because: You are the assignee for the bug.
