New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user

Issue metadata

Status: Assigned
Last visit > 30 days ago
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression

Sign in to add a comment

Issue 914911: Black screens galore

Reported by, Dec 13

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36

Steps to reproduce the problem:
Use Chrome
Browse the web
Open a bunch of tabs

What is the expected behavior?
No black screen

What went wrong?
As of a few weeks ago I am seeing completely black screens intermittently when using Chrome browser, something I never saw before. Perhaps a memory management issue? I have plenty of available memory though. Last week I had a ton of chrome tabs open and the black screen would not go away so I had to close chrome. Upon re-opening it would let me restore the tabs but as soon as they all loaded I got a black screen again. No way out of it. I ended up having to lose all of my tabs. Now I am seeing completely black screens when using Chrome more and more often, some times they stick on for a few seconds. Worried as soon as I have too many tabs open it will stay black like last time.

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? Yes I keep my Chrome updated, this started a few weeks ago, unsure of precise version

Chrome version: 71.0.3578.80  Channel: stable
OS Version: 10.0
Flash Version:

Comment 1 by, Dec 13

Labels: Needs-Feedback
Can you provide a screenshot? And information from chrome://gpu

Comment 2 by, Dec 13

I can try to snag a screen shot next time it happens but the Chrome window literally becomes an entire black screen. I can grab chrome://gpu next time it happens for a few seconds but cannot get it when it stays black because Chrome is not usable at all at that point.

Comment 3 by, Dec 13

Project Member
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit - Your friendly Sheriffbot

Comment 4 by, Dec 13

Components: Internals>Compositing
We typically see sets of black squares for GPU memory and tiling issues. I wondered if that was what you were seeing (hence the screenshot). Providing the gpu info even just now can give us some idea of the GPU you are running.

Comment 5 by, Dec 13

It was not sets of black squares. The entire application window turns black. Can't see anything at all but solid black. Other apps on computer continue to work without issue but as soon as chrome is clicked to bring back in focus, its black.

I will get the GPU info now

Comment 6 by, Dec 13

GPU info attached
Chrome GPU.txt
52.2 KB View Download

Comment 7 by, Dec 14

Status: Assigned (was: Unconfirmed)
Zmo@, can you help find an owner for this issue - may be Windows specific. Don't see any red flag experiments (oop-d/oop-r) in GPU info.

Comment 8 by, Dec 14

FYI there are a few similar reports in the Google Chrome Product Forums so I am not the only one experiencing

Please let me know if I can provide any additional logs or run anything outside of chrome to help pinpoint when the error occurs.

Comment 9 by, Dec 14

geofflang@, jmadill@: although may not related to the blackness, but this error message looks suspicious:

[1244:10836:1212/] : EGL Driver message (Error) eglMakeCurrent: Bad access.

I don't know the ANGLE's EGL implementation so could you help shedding some light here. What could be the possible reason MakeCurrent failed?

This is an Optimus dual GPU system (although about:gpu says it's not).

My suspicion of the black window is due to Chrome falling back to SwiftShader and somehow get stuck in a bad state for a bit (or for a long time).

josh@: can you turn on logging:

and when the black window happens again, shut down Chrome and send us the log file from your system. (if you don't want to share it publicly here, please send it to

Comment 10 by, Dec 14

There is still a possibility Chrome ran out of certain types of VRAM. Since it's Optimus, when running with NVidia, NVidia's VRAM is per resource type, so say your total VRAM may still be available, but the system may running out texture VRAM, things like that. Hopefully if that's the case, we will be able to see an OUT_OF_MEMORY error in the log, if you don't mind sharing.

Comment 11 by, Dec 14

Looking at the code, eglMakeCurrent can only fail with a BAD_ACCESS error when the low-level D3D11 internals fail (either creating a resource or applying the context's state).  This looks like an edge case in our conversion of internal errors to EGL errors where the message gets dropped, going to add some extra logging and it may point us to what error is being generated.

Comment 12 by, Dec 14

geofflang@: thanks. Assign this to you to enhance error handling. Then feel free to assign it back to me.

Comment 13 by, Dec 15

Project Member
The following revision refers to this bug:

commit 7139b434210c8c168aece65022ee9196c2bf550b
Author: Geoff Lang <>
Date: Sat Dec 15 16:39:47 2018

Print a warning on unexpected internal errors.

The error message can be dropped when converting angle::Result to egl::Error.
This makes sure something is always printed when we get an unexpected error.


Change-Id: Icc8b06b1c13e3ea83287da5a217f4c8bc218deec
Reviewed-by: Jamie Madill <>
Commit-Queue: Geoff Lang <>


Comment 14 by, Dec 15

Project Member
The following revision refers to this bug:

commit 13d96421161d20393a537b804904f65ed4d86c3f
Author: chromium-autoroll <>
Date: Sat Dec 15 18:05:57 2018

Roll src/third_party/angle f307584255da..7139b434210c (1 commits)

git log f307584255da..7139b434210c --date=short --no-merges --format='%ad %ae %s'
2018-12-15 Print a warning on unexpected internal errors.

Created with:
  gclient setdep -r src/third_party/angle@7139b434210c

The AutoRoll server is located here:

Documentation for the AutoRoller is here:

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.



Change-Id: Idc2893e4d44b9806592fad7c1b8a203905ec4b5f
Reviewed-by: chromium-autoroll <>
Commit-Queue: chromium-autoroll <>
Cr-Commit-Position: refs/heads/master@{#616987}

Comment 15 by, Dec 17

josh: I added more logging that should show up in Chrome version 73.0.3642.0.  If you use Chrome canary and upload about:gpu for us again, hopefully it will have more information to diagnose this.

zmo: I'm about to go on vacation for the holidays, going to send this back to you until I'm back.

Comment 16 by, Dec 17

Ok I will await the update to come through and report back

Interesting enough, I updated from Windows 1803 to 1809 as well as updated my computer's drivers and now what used to be black screens seem to be presenting as complete freeze ups of chrome. I check Task Manager each time and 80% of CPU and 60% of RAM is available... Just surfing various websites, not using one in particular. All extensions disabled.

Comment 17 by, Dec 17

Ok I got 73.0.3642.0 and will run to see what happens

Have a great vacation and Holiday!

Comment 18 by, Dec 18

Freeze ups continue and now instead of black screens I am seeing completely white screens. Only Chrome is freezing. Still at least 50% RAM and 50% available at all times this is occurring. I dont even have many tabs open compared to what I usually do. Log attached from right after the last freeze up/white screen. Will upload another if it happens again.
Chrome GPU2.txt
141 KB View Download

Comment 19 by, Dec 18

+tdresser@: see the #18 attachment. What does this mean?

[13496:13288:1218/] : Surface::TakeLatencyInfoFromFrame, LatencyInfo vector size 102 is too big.

Comment 20 by, Dec 18

Out of curiosity, is there a way to see what tab is taking up memory, either in real-time or in a log? I have one dozen tabs open (usually several dozen) and Canary is currently eating 8-9 GB of RAM for only one dozen tabs. I have never seen stable Chrome use so much. Is that normal for Canary? Thanks

Comment 21 by, Dec 18

You can open menu->More Tools->Task Manager

Right click on the first row to add more columns to watch

Comment 22 by, Dec 28

Completely black screens are happening again

I took another log for your review (attached)

Looking at my computer's task manager, plenty of RAM, CPU, GPU left. Chrome was only using a few GB out of the 16 GB of RAM.
Chrome GPU3.txt
143 KB View Download

Comment 23 by, Dec 30

So very interesting thing happening now. Whenever I go to open a new tab, drag it to its own window (separate from other tabs), Chrome goes black and stays black. I can press ctrl-w and it closes the tab and I can go back to using chrome again but if I try to open a new tab and drag to a new window, the same thing happens. Attached is a screenshot.
chrome black screen.png
16.7 KB View Download

Comment 24 by, Dec 30

And another screenshot

Comment 25 by, Dec 30

And another screenshot
chrome black screen2.png
321 KB View Download

Comment 26 by, Jan 2

+sadrul, see #19.

Comment 27 by, Jan 3

error message from #22 is interesting. There are a lot of "glSetDrawRectangleCHROMIUM: failed on surface"

Unfortunately the reason SetDrawRectangle failed on the surface is a DLOG. Let me fix that and then you can run Canary with the fix so we could understand what's going on there.

Comment 28 by, Jan 5

Project Member
The following revision refers to this bug:

commit bccf0827db6115a8fac5b0ab7ad2babe5d1d597a
Author: Zhenyao Mo <>
Date: Sat Jan 05 03:00:23 2019

Add VLOG to DirectCompositionChildSurfaceWin::SetDrawRectangle

This is for investigation purpose and will revert after this gets
in Canary and we get the error message from user.


Change-Id: I67761a335c7e6dee36a2beb8c593f03c4b2d1958
Reviewed-by: Antoine Labour <>
Commit-Queue: Zhenyao Mo <>
Cr-Commit-Position: refs/heads/master@{#620164}

Comment 29 by, Jan 7

josh: can you run again on the latest Canary (check about:version, make sure it's 73.0.3664.1 or newer). When you are able to reproduce the issue, provide the about:gpu data again. Hopefully it will get the error messages I just baked into Canary build.

Comment 30 by, Jan 8

ok i updated and will report back with data when it happens again, thanks

Comment 31 by, Jan 14

So interestingly enough, Chrome seems much more stable all of the sudden. I will continue using but I was generally getting the black screens and freezing several times a day. It has not happened in almost an entire week. I have been updating Chrome Canary daily. Was there a code change? I also happen to run a Windows update (latest monthly cumulative for Win 10 1809) last week around the same time so unclear if that may have played a role.

Comment 32 by, Jan 30

Its happening again, quite frequently. This time when watching a video on Showtime Anytime. Log attached.
Chrome GPU4.txt
143 KB View Download

Comment 33 by, Feb 4

As of late the frequency of black screens has increased substantially. I basically cannot use Chrome today. Every window I open or new tab yields a black screen.

Comment 34 by, Feb 7

Josh: Sorry I forgot to mention it earlier, but could you always run Chrome with --enable-logging --v=1? So when the black screen happens again, provide the about:gpu content to us. The logging I added before won't be captured by default.

Comment 35 by, Feb 14 (4 days ago)

No black screens today but uploading both the error log and about gpu log. I will report back if I get any and with new logs at that time.
canary gpu1.txt
15.7 KB View Download
canary gpu1_aboutgpu.txt
116 KB View Download

Comment 36 by, Feb 14 (4 days ago)

Thank you, Josh.

Comment 37 by, Yesterday (41 hours ago)

Still not getting the black windows like I usually do but am now seeing momentary black covering text boxes / forms within tabs. Very strange. I am attaching some fresh logs from the past couple days in case there is anything of use.
canary gpu2.txt
7.7 KB View Download
canary gpu2_aboutgpu.txt
115 KB View Download

Sign in to add a comment