Issue metadata
Sign in to add a comment
|
After update from v51 to v53 Chrome does not display any site text
Reported by
pierrevh...@gmail.com,
Sep 21 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0 Steps to reproduce the problem: Note: Our RHEL 7 install is very basic. No X-server. We use it to run headless tests in Selenium. I created screenshots via Xming. 1. open a site e.g. www.google.com 2. No text is shown, only graphics. E.g. the text in the buttons is invisible. If you select-and-copy and then paste into a text doc, the text is visible. So text is present in the browser. It just does not display. 3. Open Chrome's menu. Text displays properly. 4. Choose Developer tools. No text is shown, only graphics. 5. Open a text-heavy site e.g. nytimes.com. Some text is shown. E.g. the text in <a href>'s is visible. But text in <li> or <p> isn't. What is the expected behavior? Allt text on the site and in menu's is shown. What went wrong? Not all text is shown Did this work before? Yes In stable-51.0.2704.106-1.x86_64 it worked OK Chrome version: Google Chrome 53.0.2785.116 Channel: stable OS Version: Red Hat Enterprise Linux Server release 7.2 (Maipo) Flash Version:
,
Oct 26 2016
After some research we discovered the problem is caused by missing fonts. Our fix: yum install liberation-sans-fonts-1.07.2-15.el7.noarch liberation-mono-fonts-1.07.2-15.el7.noarch This issue can be closed
,
Nov 4 2016
51.0.2704.106 and before work, 52.0.2743.116 and after do not. bisect-builds.py: You are probably looking for a change made after 391137 (known good), but no later than 391152 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/efaf1b116773bbbc1b5e77358171f8c8d6b6b771..23fff35c8f6011affb8c3025b5e4ec3e82c13bb0 Just adding the two fonts mentioned in #2 only fixed part of the problem. "yum install liberation-*" fixed more, but there are still some missing characters and the text that does show up is hard to read. The attached screenshots are from a brand new CentOS 7 minimal install. The one with very little text shows "Help/About Google Chrome" in the background and the sign-in box in the foreground before I installed the above fonts. The second one is after. Is the requirement of external fonts to be expected? What other fonts need to be installed? Are there better fonts than liberation* that would make the url etc. more readable? Is there a reason these fonts are not listed as dependencies so Yum installs them automatically?
,
Dec 1 2016
Available Packages liberation-fonts-common.noarch 1:1.07.2-15.el7 base liberation-mono-fonts.noarch 1:1.07.2-15.el7 base liberation-narrow-fonts.noarch 1:1.07.2-15.el7 base liberation-sans-fonts.noarch 1:1.07.2-15.el7 base liberation-serif-fonts.noarch 1:1.07.2-15.el7 base
,
Dec 1 2016
,
Jan 5 2017
55.0.2883.87 won't even start without liberation-* installed. Trying to launch from the GUI shows nothing, not even an error message. From a CLI I get "Illegal instruction". Crash dump id: 3df5889080000000. There is nothing telling the user that the problem is missing fonts. Text is still hard to read and has missing characters as noted in Comment 3.
,
Jan 13 2017
Unable to reproduce the issue on Ubuntu 14.04 using stable 55.0.2883.87(changing the Chrome language to nl as well). Possible suspect from the above CL from comment#3: Review-Url: https://codereview.chromium.org/1939203002 Stack trace for :3df5889080000000(comment #5) ============================================ Thread 0 CRASHED [SIGILL @ 0x00007f84c3ad8c4b ] MAGIC SIGNATURE THREAD Stack Quality86%Show frame trust levels 0x00007f84c3ad8c4b (chrome -./out/Release/../../ui/gfx/platform_font_linux.cc:63 ) CreateSkTypeface 0x00007f84c3ad8936 (chrome -./out/Release/../../ui/gfx/platform_font_linux.cc:112 ) gfx::PlatformFontLinux::PlatformFontLinux 0x00007f84c3ad96e5 (chrome -./out/Release/../../ui/gfx/platform_font_linux.cc:308 ) <name omitted> 0x00007f84c3ad8648 (chrome -./out/Release/../../ui/gfx/font.cc:16 ) <name omitted> 0x00007f84c3abac24 (chrome -./out/Release/../../ui/gfx/font_list.cc:218 ) <name omitted> 0x00007f84c3abaa98 (chrome -./out/Release/../../ui/gfx/font_list.cc:95 ) <name omitted> 0x00007f84c3ad2a70 (chrome -./out/Release/../../ui/gfx/render_text.cc:1052 ) <name omitted> 0x00007f84c3ada2b8 (chrome -./out/Release/../../ui/gfx/render_text_harfbuzz.cc:771 ) <name omitted> 0x00007f84c3ace9d5 (chrome -./out/Release/../../ui/gfx/render_text.cc:446 ) <name omitted> 0x00007f84c4349101 (chrome -./out/Release/../../ui/views/corewm/tooltip_aura.cc:71 ) <name omitted> 0x00007f84c434907c (chrome -./out/Release/../../ui/views/corewm/tooltip_aura.cc:159 ) <name omitted> 0x00007f84c43231db (chrome -./out/Release/../../ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc:483 ) views::DesktopWindowTreeHostX11::CreateTooltip 0x00007f84c434d340 (chrome -./out/Release/../../ui/views/widget/desktop_aura/desktop_native_widget_aura.cc:484 ) <name omitted> 0x00007f84c4c3fd1b (chrome -./out/Release/../../chrome/browser/ui/views/frame/desktop_browser_frame_aura.cc:62 ) <name omitted> 0x00007f84c4317197 (chrome -./out/Release/../../ui/views/widget/widget.cc:339 ) <name omitted> 0x00007f84c4bcb393 (chrome -./out/Release/../../chrome/browser/ui/views/frame/browser_frame.cc:100 ) <name omitted> 0x00007f84c4a88a9b (chrome -./out/Release/../../chrome/browser/ui/views/frame/browser_window_factory.cc:18 ) <name omitted> 0x00007f84c49f23dd (chrome -./out/Release/../../chrome/browser/ui/browser.cc:258 ) <name omitted> 0x00007f84c4a154d4 (chrome -./out/Release/../../chrome/browser/ui/startup/startup_browser_creator_impl.cc:446 ) <name omitted> 0x00007f84c4a14b3e (chrome -./out/Release/../../chrome/browser/ui/startup/startup_browser_creator_impl.cc:1065 ) <name omitted> 0x00007f84c4a145d5 (chrome -./out/Release/../../chrome/browser/ui/startup/startup_browser_creator_impl.cc:1006 ) <name omitted> 0x00007f84c4a13da9 (chrome -./out/Release/../../chrome/browser/ui/startup/startup_browser_creator_impl.cc:893 ) <name omitted> 0x00007f84c4a135b5 (chrome -./out/Release/../../chrome/browser/ui/startup/startup_browser_creator_impl.cc:382 ) <name omitted> 0x00007f84c4a11b79 (chrome -./out/Release/../../chrome/browser/ui/startup/startup_browser_creator.cc:369 ) <name omitted> 0x00007f84c4a11240 (chrome -./out/Release/../../chrome/browser/ui/startup/startup_browser_creator.cc:736 ) <name omitted> 0x00007f84c4a10746 (chrome -./out/Release/../../chrome/browser/ui/startup/startup_browser_creator.cc:324 ) <name omitted> 0x00007f84c3260622 (chrome -./out/Release/../../chrome/browser/chrome_browser_main.cc:1999 ) ChromeBrowserMainParts::PreMainMessageLoopRunImpl 0x00007f84c325e9dc (chrome -./out/Release/../../chrome/browser/chrome_browser_main.cc:1384 ) ChromeBrowserMainParts::PreMainMessageLoopRun 0x00007f84c2970ff3 (chrome -./out/Release/../../content/browser/browser_main_loop.cc:964 ) content::BrowserMainLoop::PreMainMessageLoopRun 0x00007f84c2c33f65 (chrome -./out/Release/../../base/callback.h:64 ) <name omitted> 0x00007f84c296f540 (chrome -./out/Release/../../content/browser/browser_main_loop.cc:854 ) content::BrowserMainLoop::CreateStartupTasks 0x00007f84c297331a (chrome -./out/Release/../../content/browser/browser_main_runner.cc:140 ) content::BrowserMainRunnerImpl::Initialize 0x00007f84c296c213 (chrome -./out/Release/../../content/browser/browser_main.cc:42 ) content::BrowserMain 0x00007f84c302ac13 (chrome -./out/Release/../../content/app/content_main_runner.cc:779 ) content::ContentMainRunnerImpl::Run 0x00007f84c302973d (chrome -./out/Release/../../content/app/content_main.cc:20 ) content::ContentMain 0x00007f84c1ddda9c (chrome -./out/Release/../../chrome/app/chrome_main.cc:97 ) ChromeMain 0x00007f84ba839b34 (libc-2.17.so + 0x00021b34 ) 0x00007f84c1ddda4f (chrome + 0x00b27a4f ) SyscallAsm 0x00007f84c1ddd913 (chrome + 0x00b27913 ) 0x00007f84c10a31e2 (ld-2.17.so + 0x0000f1e2 ) 0x00007f84c1ddd913 (chrome + 0x00b27913 ) 0x00007f84c1ddd93c (chrome + 0x00b2793c ) _start Crashes are not seen on M56 and M57 channels so far. Omahaproxy UI CL: https://chromium.googlesource.com/chromium/src/+log/53.0.2785.0..54.0.2840.0?pretty=fuller&n=10000 Possible suspect : Review-Url: https://codereview.chromium.org/2124633002 j.isorce@samsung.com/drott@: Could you please take a look into this if its related to your change.
,
Jan 13 2017
Could it be that the CL above landed in M55 and that its follow-up/rework has landed on M56 with https://codereview.chromium.org/2347383002 ? That could explain that it fails on M55 and works on M56/M57. If yes one could back port it or revert initial 2124633002.
,
Jan 13 2017
56.0.2924.59 and 57.0.2979.0 also yield SIGILL on startup without a seperate font package installed. Installing liberation-* or abattis-cantarell-fonts (as noted at https://bugs.chromium.org/p/chromium/issues/detail?id=676728 ) allows all three versions to start correctly and show the majority of text.
,
Jan 13 2017
417276 shows no text unless externals font(s) are installed 417284 yields SIGILL unless externals font(s) are installed CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/97647b7f0ade60db7dca0d6f2d57e2f8dd79cc20..04f74a5b5283f1e38fcf21ed684267cd13053e02
,
Jan 18 2017
From the changelog range, in "7834a17 Activate Skia SFNT filter, avoid Type 1 fonts by drott" we're intentionally deprecating the usage of Type 1 fonts. Perhaps your initial basic package selection provided some Type1 fonts which were previously used by Chrome and sufficient to display some text. However, in order to optimize our font code in Blink for performance and reduce code complexity we decided to remove support for such fonts. For a discussion, see issue 632142 . Font selection in Blink and Chrome UI is slightly different but in both cases, a default font or a last resort font is needed. On Linux, both Chrome UI and Blink rendering use fontconfig to match fonts. As you can see from https://codereview.chromium.org/2278143002 as a general rule Fontconfig needs to provide at least physically available fonts for "Sans" and "Sans-Serif". If your system and package configuration does not provide any of those, Chrome might not start correctly. A workaround might be to update your Fontconfig confuration to point to compatible TrueType or OpenType fonts using TrueType or CFF outline formats, but not Type 1 fonts. An alternative workaround might be to choose available Fonts as default for Sans serif and Serif in your Chrome preferences. I am closing this bug as WontFix since we're relying on the system to have reasonable default fonts available. Please reopen if you disagree with this assessment. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by schizphr...@gmail.com
, Sep 21 2016