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

            Bug ID: 161459
           Summary: [PERF] [HighCPU] Slow initial loading using embedded
                    Fonts
           Product: LibreOffice
           Version: 24.2.3.2 release
          Hardware: x86-64 (AMD64)
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: LibreOffice
          Assignee: [email protected]
          Reporter: [email protected]

Description:
When opening the attached file, the initial loading of the file is crazy slow.

This is very likely because of the attached 5 fonts bloating that file to 1.7
MB in total.

The behavior is crazy on a macbook 2014 with


Version: 24.2.3.2 (X86_64) / LibreOffice Community
Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba
CPU threads: 4; OS: macOS 11.7.10; UI render: Skia/Raster; VCL: osx
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

On my newer HP ProBook Ubuntu laptop, it is much better. 
Version: 24.2.3.2 (X86_64) / LibreOffice Community
Build ID: 420(Build:2)
CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Ubuntu package version: 4:24.2.3~rc2-0ubuntu0.22.04.1~lo1
Calc: threaded

On my old Microsoft Surface Go it is loading really fast.

On my second mac (macbookpro 2018 with intel i7) it is loading "ok", but it is
slow compared to other files. Only exception: embedded fonts.
Version: 24.2.3.2 (X86_64) / LibreOffice Community
Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba
CPU threads: 8; OS: macOS 14.5; UI render: Skia/Raster; VCL: osx
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

Not tested on the M1, but I guess this won't be recognizable on that new
machine.



Steps to Reproduce:
open file

Actual Results:
slow opening, high CPU usage when initially loading.

Expected Results:
fast as on Windows


Reproducible: Always


User Profile Reset: No

Additional Info:
see above

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

Reply via email to