Leaflet: Setting map center to L.LatLng(Infinity, Infinity) causes infinite loop

[theashyster]

How to reproduce

• Leaflet version I'm using: master, 1.0.3
• Browser (with version) I'm using: Chrome, Firefox (latest versions)
• OS/Platform (with version) I'm using: Windows 8.1

What behavior I'm expecting and which behavior I'm seeing

I expect that passing Infinity in to the L.LatLng constructor like this new L.LatLng(Infinity, Infinity); would throw an error. Instead this is allowed and is causing the browser to freeze when adding a tile layer, for example.

Minimal example reproducing the issue

Beware, this will freeze your browser
Example - http://playground-leaflet.rhcloud.com/qem/edit?html,output

[IvanSanchez]

The problem, as far as I can see, lies within the L.GridLayer logic for the tile bounds. The for (var i = tileRange.min.x; i <= tileRange.max.x; i++) { loop in L.GridLayer._update is trying to loop from Infinity to Infinity (since those are the values of tileRange.min.x and tileRange.max.x).

So the problem is not instantiating a L.LatLng with infinite numbers, is creating a map, setting the map center's easting coordinate to Infinity, and adding one tile layer to that map.

[theashyster]

I see, okay, then we should blame the L.GridLayer.
Yep, great. On the other hand though - should the L.LatLng be initiated using infinite numbers?

[IvanSanchez]

I think that L.LatLngs should be allowed to have Infinity coordinates. We, in fact, use stuff like that for the maxBounds option of the map.

[theashyster]

Okay, I see, thanks for the explanation. ;)

[theashyster]

Looks like this is fixed in #5479
My example does not freeze the browser any more

[theashyster]

@IvanSanchez However, looks like I found another issue after the merge.
This is the same example, but with the Console part open - http://playground-leaflet.rhcloud.com/qem/edit?html,console,output

The map loads up and if you do a drag on the map the Console will continuously fill up with the newly added error Attempted to load an infinite number of tiles.

[IvanSanchez]

@theashyster Hey, you wanted Leaflet to throw an error instead of getting stuck in an infinite loop, and you got errors instead of infinite loops, don't complain now 😝😝😝

[theashyster]

@IvanSanchez Damn, I have to choose my expectations more wisely next time.

[theashyster]

@IvanSanchez Is this implementation going to stay the way it is with the error thrown continuously?

[IvanSanchez]

What would be the alternative? I can't see a good one right now :-|

[theashyster]

I played with the example a bit and looks like the error is thrown in an infinite loop basically when you do a drag and release that causes the inertia to kick in. In other words when I changed the example a bit and added inertia: false to the map options I was not able to reproduce the infinite loop of errors. Maybe that helps in finding some ways to prevent this?

[zhen1991]

Hi!
I had the same problem like u guys
Uncaught Error: Attempted to load an infinite number of tiles
when using proj4leaflet js.

[MappingSupport]

I just added masu.map.zoomIn to my code and console.log says "Error: Attempted to load an infinite number of tiles"
I have confirmed that I am providing a legit latlng.

I will investigate more and then hopefully I can make a more useful post.

Edit: Adding animate: false made no difference

More info: I am using leaflet 1.3.4, windows 10 and current versions of Firefox and Chrome.
I tried setting map options to animate: false
but that did not help.

[IvanSanchez]

Can you publish a fiddle/codepen/plunkr that displays this behaviour? I mean, something that reproduces the issue while providing a non-infinite latlng.

[MappingSupport]

Greater Seattle area was hit today with the second windstorm in less than a week. Assuming the power is on in the morning I will see if I can produce a short demo.

[MappingSupport]

Mark my comment down to 'user error'. I am a reformed Google map API dev still coming up to speed on Leaflet.

Also, I mis-spoke. Actually I was using the event setZoomAround and failed to use the correct syntax. I also failed to notice that the Leaflet API will automatically zoom in on a spot that is double-clicked. My attempt to code that feature myself is what led me down this path of confusion.

All is good now.
And the power is on.

Thanks to all the mighty minds that have made Leaflet so great!

[IvanSanchez]

I think the current approach (throw an error from #6416) is the right one - no better ones have been suggested :-|