headless - character encoding or font wrong
Reported by
9607...@gmail.com,
Sep 21
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Example URL: any Steps to reproduce the problem: 1. install prerender (https://github.com/prerender/prerender/commit/2e909d44e9bbb72e1d414d4bfc3d337ef3b01d3b) 2. visit http://localhost:3000/render?renderType=jpeg&url=https://www.google.com/ What is the expected behavior? the webpage should be rendered as a jpeg in any valid language. What went wrong? the character encoding or the font is corrupted or wrong. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 69.0.3497.100 Channel: stable OS Version: 3.10.0-862.3.2.el7.x86_64 (CentOS Linux release 7.5.1804 (Core)) Flash Version: prerender is running these processes (server.js is prerender): node server.js /usr/bin/google-chrome --headless --disable-gpu --remote-debugging-port=9222 --hide-scrollbars cat cat /opt/google/chrome/chrome-sandbox /opt/google/chrome/chrome --type=zygote --headless --headless --enable-crash-reporter /opt/google/chrome/chrome --type=zygote --headless --headless --enable-crash-reporter /opt/google/chrome/chrome --type=zygote --headless --headless --enable-crash-reporter /opt/google/chrome/chrome --type=renderer --use-gl=swiftshader-webgl --disable-databases --disable-gpu-compositing --service-pipe-token=9926584294484171314 --lang=en-US --headless --enable-crash-reporter --num-raster-threads=1 --service-request-channel-token=9926584294484171314 --renderer-client-id=2 --shared-files=v8_context_snapshot_data:100,v8_natives_data:101 /opt/google/chrome/chrome --type=gpu-process --headless --headless --enable-crash-reporter --gpu-preferences=KAAAAAAAAACAAABAAQAAAAAAAAAAAGAAAAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAA --use-gl=swiftshader-webgl --override-use-software-gl-for-tests --headless --enable-crash-reporter --service-request-channel-token=11151281908011481544 /opt/google/chrome/chrome --type=-broker
,
Sep 24
,
Sep 25
That looks like a character encoding problem.
,
Sep 26
I took the time to setup a Docker container for Centos 7 and chrome and it works fine. So I'm going to assume the server is a "customized" version of Centos (I didn't set it up, and servers have been setup with "custom os's" before in my company). Feel free to close the issue if desired, or if you are unable to reproduce the issue.
,
Sep 27
ASCII characters like "Google" are also garbled, so I guess this is a font selection problem (some symbol font was used) rather than a character-encoding problem. Let me close this, as per #c4 this does not happen in a fresh CentOS environment. |
||||
►
Sign in to add a comment |
||||
Comment 1 by vamshi.kommuri@chromium.org
, Sep 23