Another case of maximum call stack size

[jliebrand]

We're still seeing errors in production with maximum call stack size reached.

Here's an example set of coords that cause it:
https://gist.github.com/jliebrand/5b00599bee190e28d26ead782c35e988

[jliebrand]

And another one:
https://gist.github.com/jliebrand/2ed45ae989a45e701d52ca0148d5f1d5

[jliebrand]

And another one:
https://gist.github.com/jliebrand/0ebe812a5ded2564c0c6693435ba382d

(let me know if you need more)

[mfogel]

Thank you for the examples! Probably no more needed at the moment. I just need to catch up on fixing the bugs... I'm planning to get time this upcoming weekend to hopefully deep dive into at least one more.

[mfogel]

Ok I was able to simplify the first set of coordinates down to just:

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {},
      "geometry": {
        "type": "Polygon",
        "coordinates": [[[0, 0], [3, -2], [5, 0], [0, 0]]]
      }
    },
    {
      "type": "Feature",
      "properties": {},
      "geometry": {
        "type": "Polygon",
        "coordinates": [[[0, 0], [3, -1], [4, 0], [0, 0]]]
      }
    },
    {
      "type": "Feature",
      "properties": {},
      "geometry": {
        "type": "Polygon",
        "coordinates": [[[0, 0], [3, -3], [5, 0], [0, 0]]]
      }
    }
  ]
}

for which executing a union on still triggers a 'maximum call stack exceeded' error.

[mfogel]

@jliebrand The commit I just placed on master fixes things for me for the three sets of coords on this ticket, as well as the ones in #45 and #46. If the fix doesn't work for any of them for you, please reopen. And please shoot me more bugs as you run across them.

I plan to release a new minor version to npm with the latest bugfixes in a few days.