It appears that the change_stream_pit_pre_image_deletion_asymmetric.js test can end up using over 12 GB of memory across its three nodes. This can especially become an issue if the test is running in parallel with others. We should see if we can adjust this test so that it never ends up being so memory-intensive.