flamebearer Files

Features

• Hot lines for Chrome traces. Per-sample line data from DevTools recordings now feeds the hot lines section, the same way .cpuprofile data does.
• Several --stacks targets per run, repeated or comma-separated (--stacks draw,render). Names that don't match are listed up front with suggestions, and the matching ones still show.
• Original function names from source maps for bundled code (e.g. translate$2 → translate).

Fixes

• Percentages are now of thread busy time. Top CPU used busy + idle before, so a mostly idle recording squeezed every row and clipped the list. The stats line now prints active: A–B ms when there's a long idle head or tail, ready to pass to --from/--to.
• --from/--to now apply to heaviest stacks, --stacks and hot lines, not just the stats line and Top CPU. For .cpuprofile input, the hot lines split within a function is approximated from the whole profile, and the header says so.
• The Chrome trace task breakdown is in ms against total task time (tasks: 130.8 ms (compile 52.8 ms, loading 4.9 ms)), instead of percentages that could exceed 100%.
• Functions named in --stacks are kept even below the noise floor, rather than silently dropped.
• Hot lines no longer mark every function in a minified file as (inlined).
• Profiles with no line data say so (Hot lines: unavailable) instead of leaving the section out.