We suspect that the path from TopologyEventsPublisher::_scheduleNextDelivery() to ReplicaSetChangeListener::onConfirmedSet() can cause a stack overflow.

There are two frames that normally imply asynchronous work scheduling: TopologyEventsPublisher::_scheduleNextDelivery() and ReplicaSetChangeListener::onConfirmedSet(). It appears that work is scheduled and consumed inline on the networking thread, which can expand the stack past normal expectations.