GitLab

Fontconfig APIs that use the default config (config == nullptr) trigger
periodic automatic updates of font lists. When fontconfig is used on
multiple threads, as in Chromium, such a scan is able to free the default
config while it's being used by another thread.

Disable background scans to avoid this issue. This doesn't have any
effect on call sites that pass the config explicitly, including those
that pass the result of gfx::GetGlobalFontConfig().

Bug: 1004254
Change-Id: If7aa1b3d7b5823c3c93717557349a9d327ca2672
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872467Reviewed-by: Etienne Bergeron <etienneb@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707961}