Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High CPU usage with harfbuzz 7.0 #4139

Closed
chrs8 opened this issue Feb 27, 2023 · 8 comments
Closed

High CPU usage with harfbuzz 7.0 #4139

chrs8 opened this issue Feb 27, 2023 · 8 comments

Comments

@chrs8
Copy link

chrs8 commented Feb 27, 2023

After upgrading harfbuzz from 6.0 to 7.0 I observe high CPU usage when scrolling inside neovim in kitty terminal (see kovidgoyal/kitty#6030)

Investigating with perf top reveals:

Overhead  Shared Object                   Symbol
  56,65%  libfreetype.so.6.19.0           [.] TT_RunIns

These calls don't occur with harfbuzz 6.0

@behdad
Copy link
Member

behdad commented Feb 27, 2023

Humm. We didn't make any changes in how we interact with freetype.

@chrs8
Copy link
Author

chrs8 commented Feb 27, 2023

Any hints where I could investigate further?

@behdad
Copy link
Member

behdad commented Feb 27, 2023

Does the upgrading to HB7 also upgrade FreeType by any chance?

@chrs8
Copy link
Author

chrs8 commented Feb 27, 2023

I'm on Archlinux and this issue came with the update of harfbuzz, freetype was upgraded a couple of days earlier.
Current config:
Freetype2 2.13.0
Harfbuzz 7.0.1
-> the issue as described

If I downgrade Harfbuzz to 6.0.0 with everything else unchanged
-> no problem

@behdad
Copy link
Member

behdad commented Feb 27, 2023

Okay I did change some. My bad I think. Let me get to the bottom of this.

@behdad behdad closed this as completed in 62fc27f Feb 27, 2023
@behdad
Copy link
Member

behdad commented Feb 27, 2023

Fixed it I think. Any chance you can test?

@chrs8
Copy link
Author

chrs8 commented Feb 27, 2023

tbh, as I haven't done this before, I'd rather not mess with compiling and installing such a "low level" package myself. I will report back when the next release has made it to the arch repo.

Thank you for the fast response.

@behdad behdad mentioned this issue Feb 27, 2023
@chrs8
Copy link
Author

chrs8 commented Feb 28, 2023

Ok, I decided to take the risk and tested it.

The problem is fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants