The geoSearch command (GeoHaystackSearchCommand) uses the unsafe numberInt() method for the 'limit' and 'maxDistance' arguments. This means passing NaN will have different behavior on different platforms.

limit NaN:

• x86: effectively no limit.
• arm: empty results.

maxDistance NaN:

• x86: empty results.
• arm: point query.

Ideally the parser should reject this argument since it doesn't make sense.