The assignment operator of ReservedMemoryRegion doesn't clear the initial committed regions list, so the original committed regions are still present after the assignment (and can even be outside of the new reserved region).

As far as I can see this code is only triggered when a reserved region of a stack was not properly unregistered via ThreadStackTracker::delete_thread_stack() when a thread ends. So it should happen very rarely, if at all.