Issue metadata
Sign in to add a comment
|
Black screen in display large text file in Chrome |
||||||||||||||||||||||
Issue descriptionChrome Version: Google Chrome 61.0.3163.79 (Official Build) (64-bit) OS: Linux 4.4.0-89-generic, Goobuntu What steps will reproduce the problem? (1) Open https://uberchromegw.corp.google.com/i/chromeos/builders/betty-vmtest-informational/builds/11/steps/VMTest/logs/stdio (2) Wait for some time for the logs to be loaded into page (3) Try hitting Home/End, page down/up few times What is the expected result? The result of the logs text What happens instead? Some black blocks in the screen or whole black screen
,
Sep 21 2017
Which board has this issue? Similar issue on kevin: http://crbug.com/767002
,
Sep 21 2017
This is happening on my machine local Goobuntu workstation. And only happen when I try to access the builder log file. So, I do not think it is related to Chrome OS board configuration but Chrome's issue.
,
Sep 21 2017
I feel it's some chrome issue that when the logs are too long, they cannot be displayed well, so I will move it back to Chrome component.
,
Sep 21 2017
as this is specific to ChromeOS infra, Infra>Client>ChromeOS is the correct component.
,
Sep 21 2017
Even though I thought it should belongs to Chrome component, but I can't repro issue 767002 in my local workstation. Everything works fine and good when I scrolling the system_logs.txt file. Since I thought it might be fixed by recent Chrome uprev, I double checked if this issue still exist or not. I tried to open builder's log and scroll as much as I can. The image is the screenshot of my browser. Is it possible that Chrome has some issue with handling dynamically loaded text?
,
Sep 22 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by efoo@chromium.org
, Sep 18 2017