Alexey Alexandrov

This seems reasonable to support and the change does look simple enough. I was going to ask whether the switch to hardcode `llvm-symbolizer-14` means older version support would break but...

Ack, thanks! Will review the PR when you have it (no rush, the pace is up to you).

Probably yes, we should keep it open - I would say at least until we have one happy-path test for each view and filtering feature.

Could you attach the profile and the binary?

No response, so closing.

I think `CpuProfiler::StartProfiling` does some JIT code logging / dumps so that may need to be optimized. I think we touched on this in b/112464936#comment12 before. It would be good...

https://github.com/nodejs/diagnostics/issues/444 is related to this I think.

What does the duration field contain for such profiles?