In the process of doing SERVER-112058 we discovered that the function wraps every call in a writeConflictRetry loop even if they are exclusively doing reads.

If the loop were to encounter a write conflict, it would abandon the snapshot and potentially cause an existing collection acquisition to have a stale pointer. This has the potential to result in a system crash or undefined behaviour.