Add Tracing.requestMemoryDump method to DevTools API (protocol)

Source/devtools/protocol.json

Index: Source/devtools/protocol.json
diff --git a/Source/devtools/protocol.json b/Source/devtools/protocol.json
index b322e651e2e64b719161519e39829f14cc15c8c2..47481fdeae327ea141957716b10fb0732f38cb0c 100644
--- a/Source/devtools/protocol.json
+++ b/Source/devtools/protocol.json
@@ -4713,6 +4713,16 @@
                     { "name": "categories", "type": "array", "items": { "type": "string" }, "description": "A list of supported tracing categories." }
                 ],
                 "handlers": ["browser"]
+            },
+            {
+                "name": "requestMemoryDump",
+                "async": true,
+                "description": "Request a global memory dump.",

[pfeldman, 2015/07/20 18:44:07]

Does tracing need to be started to use this one?

[petrcermak, 2015/07/21 08:03:59]

Yes, it does. The request will fail if it hasn't been started. If tracing has
been started, but the memory-infra category not enabled, the response will
return immediately success=false.

+                "returns": [
+                    { "name": "dumpGuid", "type": "string", "description": "GUID of the resulting global memory dump." },
+                    { "name": "success", "type": "boolean", "description": "True iff the global memory dump succeeded." }
+                ],
+                "handlers": ["browser"]
             }
         ],
         "events": [