Expose performance.memory in workers

Source/core/workers/DedicatedWorkerGlobalScope.h

Index: Source/core/workers/DedicatedWorkerGlobalScope.h
diff --git a/Source/core/workers/DedicatedWorkerGlobalScope.h b/Source/core/workers/DedicatedWorkerGlobalScope.h
index 1555111e9f356be45b942e5397fee9c87034eab9..11c09303107757a5fa1c660f7fe13edf2c6f2f06 100644
--- a/Source/core/workers/DedicatedWorkerGlobalScope.h
+++ b/Source/core/workers/DedicatedWorkerGlobalScope.h
@@ -43,7 +43,7 @@ struct WorkerThreadStartupData;
 class DedicatedWorkerGlobalScope : public WorkerGlobalScope {
 public:
     typedef WorkerGlobalScope Base;
-    static PassRefPtr<DedicatedWorkerGlobalScope> create(DedicatedWorkerThread*, PassOwnPtr<WorkerThreadStartupData>, double timeOrigin);
+    static PassRefPtr<DedicatedWorkerGlobalScope> create(DedicatedWorkerThread*, PassOwnPtr<WorkerThreadStartupData>, double timeOrigin, bool memoryInfoEnabled);

[abarth-chromium, 2014/01/07 06:59:16]

It's not correct to pass memoryInfoEnabled here.  We need to find a better way
to read settings on workers.  Do we have a WorkerSettings object?  Should we use
RuntimeEnabledFeatures?

[Pan, 2014/01/07 09:30:59]

Currently, workers don't have a WorkerSettings object. we can create one sit in
WorkerGlobalScope, memoryEnabled and other settings that needed could be there.
or do you mean dedicated worker should read settings of its document every time
in case it is changed?

     virtual ~DedicatedWorkerGlobalScope();
 
     virtual bool isDedicatedWorkerGlobalScope() const OVERRIDE { return true; }
@@ -61,7 +61,7 @@ public:
     DedicatedWorkerThread* thread();
 
 private:
-    DedicatedWorkerGlobalScope(const KURL&, const String& userAgent, DedicatedWorkerThread*, double timeOrigin, PassOwnPtr<WorkerClients>);
+    DedicatedWorkerGlobalScope(const KURL&, const String& userAgent, DedicatedWorkerThread*, double timeOrigin, bool memoryInfoEnabled, PassOwnPtr<WorkerClients>);
 };
 
 } // namespace WebCore