Bug 114580 - Screen Font Antialiasing Causes performance problems and needs to be retoggled with each restart
Summary: Screen Font Antialiasing Causes performance problems and needs to be retoggle...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.3.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-20 08:36 UTC by udgrafdes
Modified: 2018-02-24 09:19 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 udgrafdes 2017-12-20 08:36:51 UTC
Two (possibly related) problems. I'm unable to determine actually which state the screen font anti-aliasing is in due to it, as well.

First off, screen font antialiasing causes performance problems. In calc, it takes multiple seconds after I enter anything in a cell before it displays. This seems to be corrected when I toggle screen font antialiasing in Tools->Options->Libreoffice->View

When I restart the program, the actual state appears to be reset, but the checkbox itself is not (it remains in whatever state I last had it). So I cannot even tell if antialiasing is enabled or disabled to get the performance problems.

This problem occurs whether or not I toggle hardware acceleration, opengl, or "use antialiasing" on the right side of this menu.

In face, I'm not sure what the practical difference between "screen font antialiasing" and "use antialiasing", as the tooltip simply says "restart required" for the latter, and the former has no tooltip. Is the latter for the interface? The former seems reasonably self-explanatory, though.
Comment 1 Buovjaga 2017-12-26 16:34:29 UTC
Do you get the same performance hit with an AppImage daily build? http://libreoffice.soluzioniopen.com/
Comment 2 Xisco Faulí 2018-01-29 17:23:13 UTC Comment hidden (obsolete)
Comment 3 udgrafdes 2018-02-24 07:00:29 UTC
Sorry for the delay. These issues seem to be mostly resolved in 6.0.1.1.

I noticed some other oddness with 6.0.1.1, such as the HW Accel checkbox being disabled when the use OpenGL checkbox was active. This might be intentional, I could be wrong. Is "Use OpenGL for Rendering" really "Use software opengl for rendering" vs "use hardware opengl for rendering"? If this is not the case, then I will probably check the daily and see if this is present there.

Has anyone been able to explain what the difference between "Antialiasing" and "Screen Font Antialiasing"? Is one *everything* vs the other *just fonts*?

I'll let you set the status on this one, according to whatever you think makes sense. I'm setting it as unconfirmed/fixed.
Comment 4 Buovjaga 2018-02-24 09:19:46 UTC
(In reply to udgrafdes from comment #3)
> Sorry for the delay. These issues seem to be mostly resolved in 6.0.1.1.
> 
> I noticed some other oddness with 6.0.1.1, such as the HW Accel checkbox
> being disabled when the use OpenGL checkbox was active. This might be
> intentional, I could be wrong. Is "Use OpenGL for Rendering" really "Use
> software opengl for rendering" vs "use hardware opengl for rendering"? If
> this is not the case, then I will probably check the daily and see if this
> is present there.

It is intentional. "Use OpenGL for Rendering" will use your graphics card for rendering the user interface. There are a lot of problems on Linux with it.

> Has anyone been able to explain what the difference between "Antialiasing"
> and "Screen Font Antialiasing"? Is one *everything* vs the other *just
> fonts*?

I guess so.