https://bugs.documentfoundation.org/show_bug.cgi?id=155070
--- Comment #4 from Telesto <[email protected]> --- (In reply to Heiko Tietze from comment #3) > QA people and developers shouldn't struggle to find the user profile and > read the log file. And ordinary users should not face crashes anyway. So -1 > to make it easier to access. The whole point being that we have to ask ordinary users for feedback. Unsure if we can call bug reporters at bugzilla 'ordinary users', though. The Skia Vulkan crashes are - so it seems - highly dependent on driver + graphic chipset. QA has only limited access. Even developers unable to reproduce those crashes, which makes them pretty much unsolvable. Also keep in mind: the causes are in multiple layers. Driver issue, Skia backend-issue, implementation issue at LibreOffice. And obviously mostly some combination of all three. -- Ordinary users should not face crashes anyway. Fully agree. My personal preference would be to make Skia Vulkan opt-in. So default being Skia Raster. Performance is decent. Not as fast as Vulkan, but not prone to crashes either as far I'm aware. Arguments: * There is no developer activity at the Skia front for a while. * The Skia Vulkan has known crashing issues - like Bug 149527 and bug 153922 * See the crash reporter stats. dll's major crashes point to dll's of graphic cards. Likely crashing once, and activating fall-back to Skia-Raster (https://crashreport.libreoffice.org/stats/) igc64.dll / igvk64.dll * The sudden crashes are causing dataloss left and right; maybe indirectly exposing some issue with document system. * People who need the extra performance can still opt for Vulkan, but usage is at their own risk. * It makes the access to the skia.log less problematic. Less users will rely on Skia Vulkan, less crashes... -- You are receiving this mail because: You are the assignee for the bug.
