The remapPrivateView() routine in Windows in version 2.0.x, used when journaling is enabled, uses VirtualProtect() to try to restore CopyOnWrite pages to their original condition. This doesn't accomplish its goal and instead causes private pages to accumulate, consuming page file space. remapPrivateView() needs to unmap and remap the private view to prevent this accumulation.
This ticket summarizes the visible symptoms and the fix for those symptoms. Making this change reintroduces
SERVER-2942 until the unmapping and remapping can be made completely reliable.