Using 1 core scrolling a slide down with arrow key
Steps to Reproduce:
1. Open the attached file (based on bug 113643)
2. Scroll the slide to top position
3. Scroll down using the down arrow key
Utilization of 1 core & a small lag
12% or less
User Profile Reset: No
Build ID: dd4f1b1bd31daf080dc0420524712dc244e539b5
CPU threads: 4; OS: Windows 6.3; UI render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2018-03-20_23:26:38
Locale: nl-NL (nl_NL); Calc: CL
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Created attachment 140880 [details]
Created attachment 140881 [details]
author Khaled Hosny <firstname.lastname@example.org> 2017-03-03 05:15:14 +0200
committer Khaled Hosny <email@example.com> 2017-03-03 13:22:53 +0000
commit a51b7a1c3a7e7cf7b0c733e1dec40288278c1884 (patch)
parent 5742868ccf030b2c0f03538d030bd18bd5666bdb (diff)
tdf#103831, tdf#100986: Force using GDI when needed
Our DirectWrite renderer is incomplete and can’t handle rotated text or text
with horizontal scaling, so route these two through GDI for now.
Don't know, if we should just dupe to bug 107521 ...?
(In reply to Buovjaga from comment #3)
> Don't know, if we should just dupe to bug 107521 ...?
It's a bit to complex for me. A commit partly reverted again because of all sorts of performance issues
http://cgit.freedesktop.org/libreoffice/core/commit/?id=5440837e02dee8bc884e02be697bfd4def621d26&h=libreoffice-5-3 (See (meta) bug 112486
The problem is still exists in LibO6.1, so must another part of same commit. Or related to bug 108608..