Geo operators are prevented inside top level $or clauses, and the $or implementation is not used when they are present outside $or clauses. However, it is possible for an exact match location query used with $or to trigger a code path disallowed for geo cursors which currently causes an fassert.

> c.ensureIndex( { a:'2d' } )
> c.ensureIndex( { c:1, b:1 } ) // This index is necessary to trigger the described behavior.
> c.save( { a:[ 0, 0 ], b:1 } )
> c.find( { a:[ 0, 0 ], $or:[ { b:1 } ] } )