I should note, I see this for a lot of URLs loaded from google.  on home page I see it give 400 errors for 

https://www.google.com/images/nav_logo242.png

and

https://www.google.com/images/branding/product/ico/googleg_lodp.ico

on google maps this tile loads

https://www.google.com/maps/vt/pb=!1m5!1m4!1i12!2i1320!3i3177!4i128!2m2!1e1!3i729!3m9!2sen!3sus!5e1105!12m1!1e4!12m1!1e47!12m1!1e3!4e0!5m2!1e0!5f2

but this one doesn't

https://www.google.com/maps/vt/stream/pb=!1m8!8m7!1m3!1i14!2i2638!3i6352!2i10!3x1612187647!3x262016!2m3!1e0!2sm!3i383077208!2m28!1e2!2spsm!4m2!1sgid!2sxfvXijKeeqClqmQjE7PPFg!4m2!1ssp!2s1!8m19!13m10!2shplexp%2Ca!18m4!5b0!6b0!8b0!9b1!22m3!6e2!7e3!8e2!19u6!19u7!19u11!19u12!19u14!19u20!20m1!2m0!3m8!2sen!3sus!5e1105!12m4!1e68!2m2!1sset!2sRoadmap!4e1!5m4!1e4!8m2!1e0!1e1!6m8!1e12!2i2!11e2!30m1!1f1.5!39b1!44e1!50e0!23i4112264&authuser=0

The only thing I can figue is that its something to do with my logged in user session.

logging out of google didn't fix it.  Logging out of chrome and starting a new session did.

Tested on Chrome Stable #59.0.3071.115 on Ubuntu16.04 and issue is not reproducible. 
 
Could someone from MTV look into this issue to verify on reported OS Ubuntu 17.04. Adding "TE-NeedsTriageFromMTV" label for further triage.

Thanks.

as I wrote, I also could not reproduce it (if using incoginto mode) and was able to fix it (by logging chromium out of google services, i.e. where I have a choice of which user to be using chromium as or guest).  Unfortunately that means I can't reproduce it all anymore, but it was a huge problem for me at the time.  It was as if something got corrupted and sometimes google https resources could be fetched and other times they couldn't.

What I should have done is in developer tools get the curl command line and see what happens, only thought of that now :/

I also get 400 errors for the tiles. 

Version 59.0.3071.115 (Official Build) (64-bit)

Signing out and restarting Chrome does not fix it.

perhaps you could do what I couldn't do, from developer tools network tab do a copy as curl for one of the ones that fail and try and see if it works on the command line?  (i.e. see if its failing because of some cookie or header that the google app itself is choking on)

I'd delete the above comment, as it probably has credentials inside of it....  and just note that curl throws the same error.

and might want to invalidate that session in case some bot snatched the credentials

Deleted comment 7 (Due to concern about credentials).  If curl is throwing the same error, presumably not a Chrome issue, or am I missing something?

well, somehow chrome and google aren't playing nice and breaking something.

I logged out of google (i.e. inside of chromium, not chromium itself) and it didn't fix it.  I deleted all my cookies and it didn't fix it.  I had to log out of chromium's integration with google itself in order to get it to work again.

Could you please collect and provide net log at the time of failure by following these instructions: 

https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

If you're still having this issue, please provide a net log as per comment #12.

experiencing it again, the google logo on the new tab page isn't loading for me.

https://www.google.com/images/branding/googlelogo/2x/googlelogo_color_272x92dp.png

Thank you for providing more feedback. Adding requester "mef@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

have 2 log files (stripped and byte level), don't really want to attach the one with my creds here.

Thanks spotter. If you're uncomfortable attaching them to the issue, feel free to send them to me directly: jkarlin@chromium.org and I'll take a look.

Looking at spotter's trace, I see that the 400 is being served from CacheStorage. So the ServiceWorker allowed a 400 to be stored when it should have discarded it. Assigning to NewTabPage (to address the NTP issue if it hasn't already been). Also adding ServiceWorker and CacheStorage components to make them aware of issues like this.

This seems unrelated to New tab page specific logic. Adding treib@ (who's working on the Desktop NTP) to double-check.
Marc, we don't do any special caching of the Google logo on the Desktop NTP, right? (i.e. we just rely on the http cache further down)

Correct, the NTP doesn't do anything special for the logo. I don't think this is related to the NTP, hence removing label.

treib@ I'm not sure I follow. NTP is served from a ServiceWorker and it fetches from CacheStorage. When I open dev-tools->Application->CacheStorage I can see the Google logo is in there. And I see in the network panel that the logo is served "from ServiceWorker". 

Yes, the NTP uses a service worker, and I'd expect the logo to be cached there. However, this bug seems to be some general problem with service workers, not related to the NTP in particular? Am I missing something?
(I assume the trace you're referencing was sent privately?)

The 'fetch' event in the NTP's serviceworker doesn't check the status of the fetch() call before putting it in the cache. In this case, it got a 400 and cached it.

I have the trace. Let me know if you need to see it.

Ah, right - huh, weird that that never caused trouble so far. I'll take care of it. Thanks for pointing this out to me!

The NTP service worker shouldn't be able to break Maps or Earth though, right? If it does, there's probably a bigger problem.

There are two issues here. The first is that Google is serving 400s to users (e.g., https://www.reddit.com/r/youtube/comments/6h59hh/400_thats_an_error_on_every_youtube_page/) that goes away when users clear their cookies (and sometimes caches as well, which makes makes me suspect CacheStorage). The second is that, at least NTP, is caching those 400s in CacheStorage which exacerbates the problem as they're reused indefinitely.

@26: Right, the NTP SW isn't affecting Maps or Earth. Either those are live 400 responses or they're also serving 400s from their CacheStorage.

ServiceWorker folks -- this is a heads up about a cachestorage usage issue that we've seen.

Josh, could you own this? If this is a regression in CacheStorage I'd rather not leave it unassigned.

Assigning to treib@ who said he would take care of it.

Note that it's not a regression in CacheStorage. It's improper usage of CacheStorage that I'm afraid we're going to see in lots of places.

Just to be clear: I'll take care of the NTP SW. I can't do anything about maps or earth.

so I should note that clearing the cache (i.e. via settings), doesn't fix the problem.  Its happening to me somewhat widely now.  In maps can't load regular tiles (satellite view works though, but dont get any of the streets names because of the former problem).  I should note that it does load the map, but then it dissappears and dragging it around doesn't help.   In maps, I also don't get the google logo at the bottom (only a small broken image type picture).

google.com (and search pages fail to show the google logo)

trying to go to gmail.com redirects me to https://www.google.com/gmail/ which fails too (but thankfully, mail.google.com which directs me to https://mail.google.com/mail/u/0/#inbox works)

to comment 32: did you try clearing cache and cookies from the last hour or as far back as it goes?

I've filed internal bug b/64675147 for the NTP service worker issue. Unassigning myself here, since this is (mostly) about maps and/or service workers in general.

cache to the beginning of time, didn't do cookies.

Removing components as the remaining issue is Google returning 400's and I don't believe this is Chrome's issue.

Your new tab page issue is cache related, but your general issue of getting 400 resources is an issue with Google services (not with Chrome, at least I don't think so). Clearing all of your cookies to beginnning of time ought to fix it.

pretty sure I deleted all cookies to the beginning of time before and it didn't fix till I logged out of chromium (annoying, lost all tabs), but this time it worked.

Thanks spotter. I'm closing this as Working as Intended because I don't believe it's a Chromium issue (aside from the NTP bug you helped to discover, thank you!). Please take this up as feedback to the services that you're having issues with.

ok, with that said, its becoming a repeated problem that chromium is getting messed up cookies / cache with google services (and obviously not just me, as at least one other person piped up here).  I'd figure some of you might have a better connection in regards to forwarding that issue, but perhaps not :/