Thanks for the issue...

As per comment #0, the issue requires corp account to test and check the above URLs. Hence, routing to inhouse team for help in further triaging. Attaching screenshot for reference.

Thanks..!

Deleted: 900660.PNG 339 KB

	900660.PNG 339 KB View Download

This looks very very much like https://bugs.chromium.org/p/chromium/issues/detail?id=898435, but that only happens with #network-service flag enabled. Is there a Finch experiment running or something like that?

Re C#2, the bug mentioned is not reproducible with network service. It also works with network service off. I think it might because network service makes loading faster and expose more corner cases in rendering. 

flagging as a release blocker for tpms. 

+ craigtumblison@, just wondering are you seeing any latest reports related to this issue? From my side, so far there is no success with the repro (Win10) based on c#0.

Thank you!

@manoranjanr Thanks for the tag!

I checked in today and it looks like the spikes we saw are starting to return to normal. Screenshots below:

Desktop: https://screenshot.googleplex.com/th7YcZ8Qqs2.png
Android: https://screenshot.googleplex.com/ApRkwQF3k7R.png

I'll ask Ernest to take another look as well just to be sure.

cool, thank you so much for the update!

Removing blocker label, since at the moment user reports related to this issue are NOT alarming.

See also https://bugs.chromium.org/p/chromium/issues/detail?id=902237

xianzhuwang@, I believe this is the issue you recently fixed. It seems we really aught to merge back to stable if at all possible.

Will merge the fix to M71.