https://bugs.documentfoundation.org/show_bug.cgi?id=155143

Marcin <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|7.5.1.2 release             |7.5.3.2 release

--- Comment #6 from Marcin <[email protected]> ---
Hello,

@Stéphane Guillou (stragu): Big thanks for help :)

I tested LO applications on both my computers (at home and at work) and after
switching to Skia/Raster I didn't see a crash anymore :) After switching to
Skia/Vulcan and a minute or two of scrolling in Writer or Calc whole LO
crashed.

Content of skia.log after crash:

RenderMethod: vulkan
Vendor: 0x10de
Device: 0x21c4
API: 1.3.205
Driver: 516.376.0
DeviceType: discrete
DeviceName: NVIDIA GeForce GTX 1660 SUPER
Denylisted: no 

I made few test installing and uninstalling different versions of LibreOffice
7:
- If I deleted the user profile after uninstalling, then Skia/Vulcan was always
enabled.
- If I left the user profile untouched after uninstalling 7.4 or 7.5 and then
installing 7.2 the settings changed to Skia/Raster.

The above behavior looks a bit strange, but it was the reason why I was still
using version 7.2. Reinstallation without deleting the user profile ensured the
stability of the application even though as a regular user I knew nothing about
Skia and Vulkan ;)

And finally: As I wrote at the beginning of this bug report, the problem
appeared not after the LO update, but after changing the monitor to a 4K model
and turning on the resolution of 3840x2160 and scaling 175%. On exactly the
same system and software, but with an FHD monitor and 100% scaling, everything
was fine.

If I understood everything correctly, then the problem is not necessarily the
LibreOffice code, but rather the graphics driver? However, it seems to me that
LO should detect such a problem somehow and can at least suggest the user to
switch to Skia/Raster after a failure.

Regards,
Marcin

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to