New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 864629 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-10-31
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

High memory usage in other gnome desktop apps when running Chrome and the Source Code Pro font

Project Member Reported by steveanton@chromium.org, Jul 17

Issue description

Chrome Version: 69.0.3494.0 (Developer Build) (64-bit)
                Revision	ca1156974cbe707fd023a00ae62104528833a44e-refs/heads/master@{#575509}
OS: Linux (gLinux)

What steps will reproduce the problem?
(1) Install the Source Code Pro font into ~/.fonts (any font? haven't tried with a different font).
(2) Start Chrome.

What is the expected result?

Running Chrome does not cause memory usage to grow in other apps.

What happens instead?

Memory usage grows unbounded in other (gnome?) desktop apps.

The rate is about 3-5 GB/min in aggregate.

Memory usage growth stops once Chrome is closed (but the allocated memory is not freed).

Also, when Chrome is running there is substantial jank in the UI (3-4 second freezes every second or so).



I ran a git bisect manually and it points to this revision: https://chromium-review.googlesource.com/c/chromium/src/+/1112179

Although it looks like that was reverted the issue still persists in the latest master (pulled today, July 17).



I dumped the memory of one of the apps that had high memory growth (csd-keyboard). It appears that most of the memory is a repetition of some binary data, but I picked out some strings (like ".fonts") . A partial dump of the repeated data is attached.



When the custom font is moved out of the ~/.fonts directory (and ~/.fonts is empty), the issue no longer happens.
 
csd-keyboard-partial-dump.txt
21.2 KB View Download
Cc: ak...@tagoh.org behdad@chromium.org
+behdad and +akira in case this is a known fontconfig issue.
I think I remember a period of fontconfig master being broken and as a result the cache updates always fail and as such all apps try to recreate the cache each time.  That can possibly result in behavior you are seeing if there's a leak in failure case in fontconfig.

All said, I think should be fixed in master.  Have you tried that?
Do you mean the system fontconfig or Chrome's fontconfig? (or both?) Chrome's fontconfig was recently updated to master.  steveanton@ is it fixed on ToT?
I verified the behavior still happens on ToT yesterday morning. Has there been a roll since then?
Yeah, I have that commit in the build.

Also: my system fontconfig is version 2.12.6-0.1
Owner: behdad@chromium.org
Status: Assigned (was: Untriaged)
NextAction: 2018-10-31
Owner: behdad@google.com
The NextAction date has arrived: 2018-10-31

Sign in to add a comment