memory.js forces an oom in a $where which can actually fail with interrupted. That can cause the next operation to oom when it uses the previous scope.

Forcing a gc before every query isn't reasonable, and the test pushes right up to system limits, so there probably isn't a good argument for fixing anything outside the test. But it would at least be good to know that the $where timed out, rather than ooming