RengundomandClaude Opus 5.5 88f8184102 fix(trace): write the benchmark file safely and off the presenter ...

Review of the benchmark report:

- The file is written to `<name>.tmp` and moved over the previous one, so a
  crash or kill during a rewrite keeps the last complete report.
- A dedicated writer keeps only the newest pending snapshot, so two reports
  can no longer be joined into one file when the writer falls behind.
- The report is formatted on the writer thread. The presenter hands over the
  kept intervals, which are shared and never copied, so the interval that
  closes no longer pays for formatting every earlier one.
- Hosts that are not x86 or report no CPU brand string leave the host fields
  out instead of failing every summary line.
- A `contentVersion` that is not a string, or does not fit, is left empty
  instead of failing the title's metadata.
- Tests cover the 240-interval rotation and `intervals_dropped`, the
  newest-only writer, the pending write on stop and the atomic replace.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-19 06:21:04 -05:00

..

include

feat(trace): record host, title and per-frame benchmark data

2026-10-19 01:01:13 -05:00

src

fix(trace): write the benchmark file safely and off the presenter

2026-10-19 06:21:04 -05:00