The point here is that if we do GC tests in jsc command-line, we're missing out on the base heap size that is experienced when you run in-browser. One way to get correct measurements is to just run in browser or in DRT/WTR. But another way would be to record the mallocs, frees, GC allocations, and GC marks that happened when running in browser (or in DRT or whatever) and then optionally replay them in jsc.
Created attachment 202890 [details] work in progress This patch does the recording. But I still need to write the replaying.