Bug 134008 - Scrolling slows down around WMF images (GDI-only)
Summary: Scrolling slows down around WMF images (GDI-only)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace, perf
Depends on:
Blocks: EMF-WMF Scrolling-PageUpDown
  Show dependency tree / graph
 
Reported: 2020-06-15 18:20 UTC by Telesto
Modified: 2024-08-14 15:27 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Perf flamegraph (122.30 KB, image/svg+xml)
2020-06-16 19:25 UTC, Buovjaga 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-06-15 18:20:43 UTC 
Description:
Scrolling slows down around WMF images (GDI-only)

Steps to Reproduce:
1. Open attachment 97742 [details] (bug 77519)
2. Scroll to page 9 -> notice a slowdown
3. Zoom in/out with CTRL+Scroll wheel .. even slower

Actual Results:
Slow

Expected Results:
As fast in 4.4.7.2 -> Nearly no lag


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: a35c18aeff3b1d8f270db7e094850fb8ba1ab84a
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL

-> Skia was disabled while testing
Comment 1 Buovjaga 2020-06-16 19:25:35 UTC 
Created attachment 162072 [details]
Perf flamegraph

It seems to be difficult to bibisect this due to the "weld FontNameBox" commit causing much CPU use in Linux 6.5 repo :(

Arch Linux 64-bit
Version: 7.1.0.0.alpha0+
Build ID: 43bdac0ebd65dfc32a0b8cf2c42fde88ad585e3f
CPU threads: 8; OS: Linux 5.7; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 15 June 2020
Comment 2 Telesto 2020-06-17 20:02:04 UTC 
Fine with
Version: 7.0.0.0.beta1+ (x64)
Build ID: 2891e91a513520d68ea2b8c59c14335861a15253
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 3 Buovjaga 2020-06-18 06:20:41 UTC 
(In reply to Telesto from comment #2)
> Fine with
> Version: 7.0.0.0.beta1+ (x64)
> Build ID: 2891e91a513520d68ea2b8c59c14335861a15253
> CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
> Locale: nl-NL (nl_NL); UI: en-US
> Calc: CL

With that commit vs. master in Linux 6.5 bibisect repo, I get the exact same CPU hit when zooming in/out.
Comment 4 Telesto 2020-06-18 06:44:21 UTC 
(In reply to Buovjaga from comment #3)
> (In reply to Telesto from comment #2)
> > Fine with
> > Version: 7.0.0.0.beta1+ (x64)
> > Build ID: 2891e91a513520d68ea2b8c59c14335861a15253
> > CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
> > Locale: nl-NL (nl_NL); UI: en-US
> > Calc: CL
> 
> With that commit vs. master in Linux 6.5 bibisect repo, I get the exact same
> CPU hit when zooming in/out.

O, sorry didn't check zoom.. anyhow illustrates my point about "weld FontNameBox"
it's the cause or hiding something.. flame graph points to "weld FontNameBox".. or something around fonts... and with only one person touching it..
Comment 5 QA Administrators 2022-08-04 03:34:14 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2024-08-04 03:23:06 UTC Comment hidden (obsolete)
Comment 7 Buovjaga 2024-08-14 15:27:10 UTC 
Testing this again with 7.0 repo on Linux and Windows and older repos, I don't see a reason to call this a regression.