Bug 142329 - FILESAVE Draw Keeps Crashing with lot of gradients shapes
Summary: FILESAVE Draw Keeps Crashing with lot of gradients shapes
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
7.0.5.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-17 13:27 UTC by lucode
Modified: 2021-12-15 04:42 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lucode 2021-05-17 13:27:33 UTC
Upgraded my LibreOffice (with fresh profile) and since then Draw isn't usable anymore. Whenever I try to save a file that contains a lot of shapes with gradients it takes minutes until it completes. Sometimes it does never end. Not sure yet but without gradients it isn't an issue.

Version: 7.0.5.2 (x64) Build ID: 64390860c6cd0aca4beafafcfd84613dd9dfb63a CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win Locale: de-CH (en_CH); UI: en-GB Calc: threaded
Comment 1 Julien Nabet 2021-05-17 14:58:57 UTC
Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile ?
Comment 2 lucode 2021-05-17 15:12:45 UTC
In my post I noted that I did start with a fresh user profile.
Comment 3 Telesto 2021-05-17 15:37:49 UTC
(In reply to lucode from comment #2)
> In my post I noted that I did start with a fresh user profile.

Disabling Vulkan rendering might help: Tools -> Options -> View -> Check Force Skia software rendering

And a sample file would be practical
Comment 4 Julien Nabet 2021-05-17 15:48:51 UTC
(In reply to lucode from comment #2)
> In my post I noted that I did start with a fresh user profile.

Oups you're right, sorry for the noise.
Comment 5 lucode 2021-05-17 15:51:15 UTC
(In reply to Telesto from comment #3)
> (In reply to lucode from comment #2)
> > In my post I noted that I did start with a fresh user profile.
> 
> Disabling Vulkan rendering might help: Tools -> Options -> View -> Check
> Force Skia software rendering
> 
> And a sample file would be practical

THX Telesto, Skia was the naughty cause of this issue. Is this a new kind of rendering?
Comment 6 Telesto 2021-05-17 17:24:03 UTC
(In reply to lucode from comment #5)
> (In reply to Telesto from comment #3)
> > (In reply to lucode from comment #2)
> > > In my post I noted that I did start with a fresh user profile.
> > 
> > Disabling Vulkan rendering might help: Tools -> Options -> View -> Check
> > Force Skia software rendering
> > 
> > And a sample file would be practical
> 
> THX Telesto, Skia was the naughty cause of this issue. Is this a new kind of
> rendering?

New for the 7.0 branch, yes. Possibly fixed with LibO 7.1/7.2. Needs testing.
And there is the driver part. Not all drivers are properly supported. 

So if you're still able to reproduce the problem with 7.2, this might be relevant (for example by blacklisting the driver; or finding the cause..
Comment 7 Julien Nabet 2021-05-17 19:00:02 UTC
Also make sure you've got last version of the driver of your graphic card (see https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28Skia.29).
Comment 8 QA Administrators 2021-11-14 04:00:59 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2021-12-15 04:42:35 UTC
Dear lucode,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp