Add configurable limit to allocations in heap profiler.

third_party/WebKit/Source/devtools/protocol.json

Index: third_party/WebKit/Source/devtools/protocol.json
diff --git a/third_party/WebKit/Source/devtools/protocol.json b/third_party/WebKit/Source/devtools/protocol.json
index 00002f8f276f9c4564031297401a94e010aea9a2..1462d7289c38f7281cb57814684f47d0acd37585 100644
--- a/third_party/WebKit/Source/devtools/protocol.json
+++ b/third_party/WebKit/Source/devtools/protocol.json
@@ -4697,7 +4697,8 @@
                 "id": "MemoryDumpConfig",
                 "type": "object",
                 "properties": [
-                    { "name": "triggers", "type": "array", "items": { "$ref": "MemoryDumpTrigger" }, "optional": false, "description": "Memory dump trigger configuration." }
+                    { "name": "triggers", "type": "array", "items": { "$ref": "MemoryDumpTrigger" }, "optional": false, "description": "Memory dump trigger configuration." },
+                    { "name": "min_allocation_size_bytes", "type": "number", "optional": true, "description": "Provides a cut off value, if a trace allocates less than that, it is discarded." }

[Primiano Tucci (use gerrit), 2016/04/21 16:53:22]

I would probably not bother exposing this to the devtools protocol, unless we
have a need for it.

[caseq, 2016/04/26 01:15:07]

Well, it gets exposed automatically since we're reusing the trace config parser.
So it's just a matter of whether we document it here or not. I've no strong
feelings towards wither way, but I think we eventually need to get
chrome://tracing wired through the DevTools protocol rather than DOM UI
bindings, as it's already doing this in case of remote tracing.

                 ],
                 "description": "Configuration for memory dump triggers. Used only when \"memory-infra\" category is enabled."
             },