see also  issue 645319 

Thanks for opening this ticket Will.

I've had this happen to me in two separate instances over the last couple days.  Once it starts happening, any navigation in any profile, in any tab, fails like this. (I had 3 different profiles open in different windows, many tabs in each profile open, but still lots of free system resources on the machine.)

The first time this started happening, I had to close all Chrome processes, *including the background process, to resolve the issue.

The second time this started happening (today), I opened the chrome task mgr to try to get a tab dump, and it seems there is no process for the semi-sad-tabs.  Of extra interest: this time, everything recovered after a period of time!  All of a sudden, I could navigate on new or existing tabs again.  That's a bit crazy.

Side note: the "dark grey" background in these traumatized tabs can also be black.  In my personal profile that I have "dark themed", the background is pure black.


- Windows 10 corp machine.
- Version 55.0.2883.87 (64-bit)
- **It appears today that Chrome has downloaded an update, is "Nearly up to date!", but needs a relaunch.  Could be related?  I never noticed this state the first time around.

I just restarted with the update, and now I'm Version 56.0.2924.87 (64-bit).  So, major revision jump.

Will update if I experience the issue again.

Is this at all related to  bug 663816 ?

This bug is solely about the correct tab not appearing when renderers cannot start for any reason.

There are other bugs for the root cause of why renderers might not be starting, including but not limited to  issue 663816 ,  issue 680366 ,  issue 645319 . I am not going to try and root cause why the renderers are not starting in this bug, but merely make the correct sad tab appear.

re: #2 & #5 I suggest you create a new bug for your issue, or hijack one of the other bugs, if you have further information to provide on what the suspected root cause of the failure to start renderers might be.

Oh, my comments definitely belong in one of the other existing tickets mentioned in #6.  Sorry.

I recommend changing the description of this ticket to explicitly focus on the visual appearance of the "sad tabs" 

wfh: Is this still happening? Is there some way to reproduce this?

@enne / 11

I saw this happen ( off of #680366 ) earlier today on 	58.0.3029.13 (Official Build) dev (64-bit) Windows 10.

Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.