Timeline addTraceProvider API

third_party/WebKit/Source/devtools/front_end/sdk/TracingModel.js

Index: third_party/WebKit/Source/devtools/front_end/sdk/TracingModel.js
diff --git a/third_party/WebKit/Source/devtools/front_end/sdk/TracingModel.js b/third_party/WebKit/Source/devtools/front_end/sdk/TracingModel.js
index 1e50f8d70a35095a674900d0e895d3d37c873d4a..8925be9a7646c67708ccc1d850909aa070fda4ba 100644
--- a/third_party/WebKit/Source/devtools/front_end/sdk/TracingModel.js
+++ b/third_party/WebKit/Source/devtools/front_end/sdk/TracingModel.js
@@ -48,6 +48,7 @@ WebInspector.TracingModel.MetadataEvent = {
     ThreadSortIndex: "thread_sort_index",
     ThreadName: "thread_name"
 }
+WebInspector.TracingModel.ExtensionEvent = "Extension";
 
 WebInspector.TracingModel.TopLevelEventCategory = "toplevel";
 WebInspector.TracingModel.DevToolsMetadataEventCategory = "disabled-by-default-devtools.timeline";
@@ -221,6 +222,11 @@ WebInspector.TracingModel.prototype = {
         var event = process._addEvent(payload);
         if (!event)
             return;
+        if (payload.name == WebInspector.TracingModel.ExtensionEvent) {

[caseq, 2016/07/11 18:58:38]

Let's avoid this. I think the right way would be either to write the trace
meta-data in the extension that would produce the desired effect or handled the
process/thread titles in the TimelineFlameChart.

+            var processName = payload.name;
+            process._setName(processName);
+            this._processByName.set(processName, process);
+        }
         // Build async event when we've got events from all threads & processes, so we can sort them and process in the
         // chronological order. However, also add individual async events to the thread flow (above), so we can easily
         // display them on the same chart as other events, should we choose so.