chrome://tracing currently records traces and then loads them into a visualizer, from which they can be saved.  Often traces are being gathered for later review, in particular when debugging high memory usage, so visualization is unnecessary, and can be actively harmful in taking time & memory. In the worst case, visualization can actually OOM the tracing renderer before the trace is saved, causing it to be lost!

chrome://tracing should be updated to simply save the trace to permanent storage immediately that capture completes, and only then to offer to re-load and visualize it.