The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/73a34473d6cc86352f226be7186e1e292fe35734

commit 73a34473d6cc86352f226be7186e1e292fe35734
Author: alph <alph@chromium.org>
Date: Thu Mar 02 23:39:49 2017

DevTools: Support reading CPU profile format on Performance panel

BUG= 697953 

Review-Url: https://codereview.chromium.org/2729793003
Cr-Commit-Position: refs/heads/master@{#454434}

[modify] https://crrev.com/73a34473d6cc86352f226be7186e1e292fe35734/third_party/WebKit/LayoutTests/inspector/tracing/tracing-timeline-load-expected.txt
[modify] https://crrev.com/73a34473d6cc86352f226be7186e1e292fe35734/third_party/WebKit/Source/devtools/front_end/timeline/TimelineLoader.js
[modify] https://crrev.com/73a34473d6cc86352f226be7186e1e292fe35734/third_party/WebKit/Source/devtools/front_end/timeline_model/TimelineJSProfile.js

Please add the OSs that this is applicable to.  Thanks!

Thanks for the fix. Please share the manual testcase for verification purpose. 
We can verify in latest canary, if all looks good please request a merge to M58.

The manual test is:
1. record a CPU profile with DevTools
2. save it to a file
3. Open performance panel
4. Load the saved profile

It should load fine.

[Auto-generated comment by a script] We noticed that this issue is targeted for M-58; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-58 label, otherwise remove Merge-TBD label. Thanks.

M-58 branch point(#454471) & CL listed at #1 is {#454434}. So no merge is needed here.