When processing the new -Xprof:file=... argument, the interpreter fails to
terminate a string copied into newly-malloced storage. Since this is in startup,
this is usually demand-zeroed anyway. However, apart from being morally wrong,
this sometimes gets a reused malloc block if argument processing is complex
enough (as it is in my profiling scripts).