chromeos-bmpblk: excessive build time due to empty font cache
Reported by
michael....@intel.com,
Sep 11 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Steps to reproduce the problem: 1. ./build_packages --board=chell 2. emerge-chell chromeos-bmpblk What is the expected behavior? Emerge of chromeos-bmpblk should take ~1.5 minutes. What went wrong? Emerge of chromeos-bmpblk takes 45+ minutes. Did this work before? N/A Chrome version: 60.0.3112.113 Channel: n/a OS Version: 10.0 Flash Version: The chromeos-bmpblk build looks in chroot/usr/share/cache/fontconfig for cached fonts. That directory is empty in the current chroot. Without the cache, the build must process the fonts multiple times, leading to a very long build time.
,
Sep 14 2017
Not really sure what component this belongs but this isn't a DevTools issue which is specifically for web developer tools.
,
Sep 20 2017
Not being discussed here but there: https://groups.google.com/a/chromium.org/d/msg/chromium-os-dev/XRcVSkWVwXo/osFyX-30AAAJ https://chromium-review.googlesource.com/#/c/669915/
,
May 28 2018
,
May 28 2018
,
May 31 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/4ba37efe5eea49ed723ec3a71f7261d3504efbc5 commit 4ba37efe5eea49ed723ec3a71f7261d3504efbc5 Author: Patrick Georgi <pgeorgi@google.com> Date: Thu May 31 10:50:24 2018 sys-boot/chromeos-bmpblk: Create ad-hoc font cache if necessary For some users (in particular those external to Google) the font cache isn't set up for whatever reason. Since the bmpblk package spawns tons of tiny processes that use font-config to write individual letters into bitmaps, and since each of these processes then proceeds to create its own in-memory cache before starting its actual work, the package takes a _very_ long time to build (there were reports of it taking several hours). Since the global cache seems to be a problem for our packaging (at least sometimes?), instead create a per-build cache: that takes an initial 20 seconds or so, but every future font use in the build is really fast. BUG=chromium:764060 BRANCH=none TEST=on a public-only repo, try `emerge-$board chromeos-bmpblk` and observe that it completes _really_ fast where without this change it doesn't. Change-Id: I552b633e14af52b5539bcfd1e2b86981dc491a8f Signed-off-by: Patrick Georgi <pgeorgi@google.com> Reviewed-on: https://chromium-review.googlesource.com/1075188 Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Tested-by: Abhijeet Kumar <abhijeet.kumar@intel.com> Tested-by: Mike Mason <mmason56@gmail.com> Tested-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-by: Abhijeet Kumar <abhijeet.kumar@intel.com> Reviewed-by: Mike Mason <mmason56@gmail.com> Reviewed-by: Stefan Reinauer <reinauer@google.com> [modify] https://crrev.com/4ba37efe5eea49ed723ec3a71f7261d3504efbc5/sys-boot/chromeos-bmpblk/chromeos-bmpblk-9999.ebuild |
|||
►
Sign in to add a comment |
|||
Comment 1 by michael....@intel.com
, Sep 11 2017