Measurers use an unreasonable amount of memory

[addisoncrump]

See issue title. When I was re-running the measurer for an experiment for which the measurers terminated early, and did not specify the runners, I OOM'd a 750GB RAM machine in a matter of minutes. The measurers stalled and ultimately returned to a stable state.

[addisoncrump]

Actually, I just had this reproduce with the number of runners specified.

[addisoncrump]

This seems to be related to the systemd fuzzer -- certain fuzzers produce inputs which cause it to OOM, but the OOM killer doesn't seem to always activate while the measurement is running.