In development, sometimes a map can crash from a mix of changing bounds and fetching locations

[wbazant]

I have not found a reproduction for this, but during development I managed to trigger this screen by accident:

It happened when using the map, on production code ( I had the commit b9e0b16 checked out).

I'm not sure what combination of mad scrolling I did means the bounds object can be null, and Redux promises this will not be shown in production, but maybe we'll see it again or find a way to reproduce it later. I've seen it more than once, and having a temporary lag on my wi-fi helps.