Screen recording. Notice the brief flash of content, and how the authentication popup does not contain a saved username/password (there is a saved u/p pair in Chrome's data that does appear maybe half of the time) - so maybe this is a failure to load from the proxy and Chrome's behavior here is now much worse.

Deleted: tab-restore.mp4 264 KB

	tab-restore.mp4 264 KB View Download

While doing some more testing, I just got a failure when it *did* save the username/password and it stayed white after logging into the proxy, so I am not sure the proxy is related at all.

Note you can also see the saved u/p if you click the little key icon in the address bar, so it definitely knows about the proxy and the saved authentication

Deleted: Screenshot 2018-04-27 22.46.52.png 16.7 KB

	Screenshot 2018-04-27 22.46.52.png 16.7 KB View Download

Thanks for filing the issue!

Unable to reproduce the issue on reported chrome version 66.0.3359.139 using Windows 10 with the below mentioned steps.
1. Launched chrome
2. Opened around 4-5 tabs, Pinned few of them.
3. Exited chrome.
4. Relaunched it again.
We were able to see all the tabs being restored properly with out any issue. Attaching the screen cast of the same.

@Reporter: Could you please have a look at the screen cast and let us know if we have missed anything in the process. It would be highly helpful if clarified on the importance of the usage of proxy in order to reproduce the issue, as we aren't using any proxy. Any further inputs from your end may be helpful.

Deleted: 837901.mp4 5.5 MB

	837901.mp4 5.5 MB View Download

I've tested this with a different proxy and it still almost always happens. I will note that audio from the page is playing while the tab is blank, so the page has fully loaded and it's just not painting the tab at all.

Sometimes merely typing text into the address bar is enough to wake it up.

This website in particular previously had an issue similar to this, https://bugs.chromium.org/p/chromium/issues/detail?id=668892. Is it possible that problem cropped up again in a different form?

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Rechecked the issue on reported chrome version 66.0.3359.139 and on the latest stable 66.0.3359.181 using Windows 10 as per the steps mentioned in comment#0 and #4. 
Note: Currently we do not have proxy(not sure...if this makes any difference) on our machines/network. 

As we are unable to reproduce the issue from our end i.e., restarting the chrome after exiting it shows all the pinned and normal tabs, hence removing Needs-Bisect label. Please feel free to add the label back if required.

From  Issue 768582  , which looks very similar to this issue, CC'ing @sdy and @pkasting for further inputs.

Thanks!

 Bug 768582  is about cases where uses close windows with pinned tabs without closing the whole app, and are surprised when Chrome doesn't try to "restore" them at all.  This bug seems to be about tabs not being restored when we fail to connect to the server.  Having no page content and no address in the address bar, and seeing about:blank on reload, is consistent with "never successfully committed the load".  I strongly suspect failed proxy authentication is to blame here; even if Chrome managed to save a login in comment 2, it could have been for a different background network load attempt, and happened after the main page content had already timed out/failed.

I don't know if there's a Chrome bug here; perhaps that we need to be more generous with timeouts and such for proxy auth during loads?  This seems like an issue for the network/loader folks.

The page loads were previously blocked on proxy authentication, and in this case it does seem like they block on authentication. Once I authenticate it starts loading the tab (I see the status messages in the bottom left, and it eventually plays music) but the tab never rasterizes, it's blank white. I can "wake it up" sometimes by interacting with the address bar or by navigating manually.

The tab is actually in a very hosed state at startup, it's not receiving or processing events at all. Not only do mouse and keyboard events not get sent to the tab, but it doesn't even get resize events. If I resize the Chrome window while the tab is in this zombie state, and then later wake the tab up by navigating, the tab is still small. See screenshot. Note that as mentioned above, the tab *has* loaded while it is in this zombie state, because it can play music.

Deleted: Screenshot 2018-05-19 06.30.26.png 1.2 MB

	Screenshot 2018-05-19 06.30.26.png 1.2 MB View Download

Gentle ping for an update from someone from the Blink>Loader team to help in further debugging.

Thanks.!

As we are unable to reproduce the issue from our end (...comment#4 and #8) hence adding label TE-NeedsTriageHelp and requesting someone from Dev team to have a look into this issue and help in further triaging.
Note: Tentatively adding component "Blink>Network" please remove if this isn't apt.

Thanks!

Definitely not Blink>Network, as that is for network APIs which would require JS to be executing. It looks like things are going wrong before it gets that far.

Adding Internals>Network for the proxy aspect of this. And UI>Browser>Navigation because something is going wrong during (startup) navigation.

Keeping Blink>Loader for the time being as I can't completely rule out a problem there.

Adding sadrul@ to check whether this is related to  issue 668892  as suggested in comment 6. If audio is playing, then it means navigation has succeeded and the document has loaded and executing, but rendering/input doesn't work.

In addition, can you share your set of variations from chrome://version?

+sunnyps@ (see comment #15).

Google Chrome	66.0.3359.181 (Official Build) (64-bit) (cohort: Stable)
Revision	a10b9cedb40738cb152f8148ddab4891df876959-refs/branch-heads/3359@{#828}
OS	Windows
JavaScript	V8 6.6.346.32
Flash	29.0.0.171 C:\Users\Katelyn\AppData\Local\Google\Chrome\User Data\PepperFlash\29.0.0.171\pepflashplayer.dll
User Agent	Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36
Command Line	"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --enable-experimental-canvas-features --enable-quic --flag-switches-end
Executable Path	C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Profile Path	C:\Users\Katelyn\AppData\Local\Google\Chrome\User Data\Default
Variations	c134752e-b8b72c88
5f419cc9-ca7d8d80
59aeb88e-3f4a17df
a6674cf-d795f81e
3095aa95-3f4a17df
d52c4ff7-d52c4ff7
47e5d3db-3d47f4f4
4dc30737-b8a5ea08
589b4e9f-3f4a17df
f9884634-659882c0
121ae2bc-ca7d8d80
57f575bb-3d47f4f4
ceff87ec-3f4a17df
44827ee5-ca7d8d80
86ba59b4-477edaa
ef05a96e-e2c3ac67
9773d3bd-f23d1dea
8e3b2dc5-93702590
9e5c75f1-1039a221
c322f799-2dbe5f9
3de1fbf2-3d47f4f4
f79cb77b-3d47f4f4
4ea303a6-85fb2903
447469ba-13d9f35f
7aa46da5-c946b150
2b33233e-1f7f5594
72606c4f-3f4a17df
58a025e3-c2b41702
2a32876a-ca7d8d80
ff29b1bd-3cfbaf8e
4bc337ce-69465896
9a2f4e5b-d226bfeb
1354da85-c7531228
494d8760-52325d43
f47ae82a-86f22ee5
3ac60855-486e2a9c
f296190c-2502111b
4442aae2-d7f6b13c
ed1d377-e1cc0f14
12e17bc5-e1cc0f14
75f0f0a0-6bdfffe7
e2b18481-4ad60575
e7e71889-e1cc0f14
b1ceb06f-d1372334
94e68624-803f8fc4
720f4871-3f4a17df
Compiler	clang

Based on the variations, Site Isolation is not enabled, so it shouldn't be affecting the behavior. This is likely something else related to input/rendering.

From my testing it seems like if I start without my typical command line args this bug doesn't happen, or is at least extremely rare. The command line args are:

--disable-direct-composition --windows10-custom-titlebar --enable-quic --origin-to-force-quic-on=tokyo.luminance.org:8001 --proxy-server="https://tokyo.luminance.org:8001" --proxy-bypass-list=127.0.0.1;localhost;203.104.248.5;game-a.granbluefantasy.jp;game-a1.granbluefantasy.jp;game-a2.granbluefantasy.jp;game-a3.granbluefantasy.jp;game-a4.granbluefantasy.jp;game-a5.granbluefantasy.jp;event-api.analytics.mbga.jp;mbga.jp;mobage.jp;app.mobage.jp;connect.mobage.jp;widget.mobage.jp;chrome.google.com;google.com;platform.twitter.com

Could custom titlebar or disabling directcomposition be the problem? It seems like they couldn't but I want to make sure that isn't a questionable one. I'm guessing it's just due to turning on the proxy since proxies get less usable with every release.