Add Web Resources usage to chrome://tracing.

third_party/WebKit/Source/core/fetch/ScriptResource.cpp

Index: third_party/WebKit/Source/core/fetch/ScriptResource.cpp
diff --git a/third_party/WebKit/Source/core/fetch/ScriptResource.cpp b/third_party/WebKit/Source/core/fetch/ScriptResource.cpp
index 347de8c64735c7c9973b08253083e3c32f3f3d9b..1b47d0854460c01c5bf038cf904b00d8326b61c9 100644
--- a/third_party/WebKit/Source/core/fetch/ScriptResource.cpp
+++ b/third_party/WebKit/Source/core/fetch/ScriptResource.cpp
@@ -33,6 +33,7 @@
 #include "platform/MIMETypeRegistry.h"
 #include "platform/SharedBuffer.h"
 #include "platform/network/HTTPParsers.h"
+#include "public/platform/WebProcessMemoryDump.h"
 
 namespace blink {
 
@@ -72,6 +73,15 @@ void ScriptResource::appendData(const char* data, unsigned length)
         client->notifyAppendData(this);
 }
 
+void ScriptResource::onMemoryDump(WebProcessMemoryDump* memoryDump) const
+{
+    Resource::onMemoryDump(memoryDump);
+    const String name = getMemoryDumpName() + "/decoded_script";
+    auto dump = memoryDump->createMemoryAllocatorDump(name);
+    dump->AddScalar("size", "bytes", m_script.string().sizeInBytes());

[haraken, 2015/09/29 02:44:48]

Just to confirm: You're special-casing ScriptResource because m_script is one of
the big memory consumers (i.e., this is not related to dumping memory of
Resources), right? That makes sense to me.

[ssid, 2015/09/29 11:06:37]

Yes, it was using extra memory(considerable) apart from the normal resource
encoded_size. So, the special case.

+    memoryDump->AddSuballocation(dump->guid(), String(WTF::Partitions::allocatorPoolNameForTracing()));
+}
+
 AtomicString ScriptResource::mimeType() const
 {
     return extractMIMETypeFromMediaType(m_response.httpHeaderField("Content-Type")).lower();