Avoid creating FontCache for memory dump.
It is possible that a memory dump will be requested before the blink font manager is set. This can result in attempting to create a fallback font manager and ignoring the real one which may be set later. Avoid this situation by ensuring that the memory dump request does not implicitly cause a global FontCache to be created just to dump that it is empty. Bug: chromium:1140954 Cq-Include-Trybots: luci.chromium.try:win_chromium_dbg_ng Change-Id: If29d830c66f85552663384898fbf3d29fb6d67e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2490503 Commit-Queue: Ben Wagner <bungeman@chromium.org> Reviewed-by:Koji Ishii <kojii@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#819842}
Showing
Please register or sign in to comment