UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2956.0 Safari/537.36

Steps to reproduce the problem:
1. Create a snippet
2. Call console.profile() and console.profileEnd() in the snippet
3. Run the snippet

What is the expected behavior?
Back when the Memory panel (formerly Profiles panel) has JS CPU profiling, a call to console.profile() from the snippet would automatically create a profile.

What went wrong?
There is no substitute for this workflow. The Performance panel does not support console.profile().

Did this work before? Yes Current Chrome Dev on Mac, which is Chrome 55

Chrome version: 57.0.2956.0  Channel: canary
OS Version: OS X 10.11.6
Flash Version: 

source: http://stackoverflow.com/questions/41145818/devtools-cpu-profiler-missing-from-chrome-canary-57/41172602?noredirect=1#comment69644024_41172602