UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/69.0.3497.81 Chrome/69.0.3497.81 Safari/537.36

Steps to reproduce the problem:
1. Build headless chromium with these args.gn:
is_debug = false
enable_profiling = true
enable_callgrind = true

2. Start it like so:
./out/Default/headless_shell --no-sandbox --enable-profiling --profiling-at-start --profiling-flush --remote-debugging-port=9222 https://youtube.com

3. Observe no chrome-profile-{process type}-{process ID} files are generated.

What is the expected behavior?
chrome-profile-{process type}-{process ID} files get generated containing CPU profiling data.

What went wrong?
chrome-profile-{process type}-{process ID} files are not generated.

From a cursory look at the code, it appears that the profiler only gets started in the Chrome layer, which would explain why it doesn't work in headless.  For example, this flag check: https://cs.chromium.org/chromium/src/chrome/common/profiling.cc?l=112&rcl=948e60271bbd01695e317c0d2bb8be041e2e73db , which looks to be called from chrome_main_delegate.cc

Did this work before? No 

Does this work in other browsers? N/A

Chrome version:   Channel: n/a
OS Version: 
Flash Version: 

Is it possible to factor CPU profiling out of the Chrome layer to make CPU profiling Headless Chromium possible?