Expose performance.memory in workers

Source/core/frame/Settings.cpp

Index: Source/core/frame/Settings.cpp
diff --git a/Source/core/frame/Settings.cpp b/Source/core/frame/Settings.cpp
index dc2bcaa6c5dc09fd25f33fc9d8dfb44ebb99372f..4a79264e62d71ec49f5be380e9c44fac8ad778d2 100644
--- a/Source/core/frame/Settings.cpp
+++ b/Source/core/frame/Settings.cpp
@@ -26,6 +26,7 @@
 #include "config.h"
 #include "core/frame/Settings.h"
 
+#include "RuntimeEnabledFeatures.h"
 #include "platform/scroll/ScrollbarTheme.h"
 
 namespace WebCore {
@@ -131,4 +132,14 @@ void Settings::setOpenGLMultisamplingEnabled(bool flag)
     invalidate(SettingsDelegate::MultisamplingChange);
 }
 
+void Settings::setPreciseMemoryInfoEnabled(bool flag)
+{
+    RuntimeEnabledFeatures::setPreciseMemoryInfoEnabled(flag);
+}
+
+bool Settings::preciseMemoryInfoEnabled() const
+{
+    return RuntimeEnabledFeatures::preciseMemoryInfoEnabled();
+}

[abarth-chromium, 2014/04/23 18:04:37]

This is incorrect.  The Settings system and the RuntimeEnabledFeatures system
are separate and should not be linked.

[Pan, 2014/04/24 00:22:28]

@abarth, @tonyg,
Currently, this setting is used as controller in perf tests.
If they are not allowed to be linked, Is it possible to remove this setting,
then pass the content_switch to perftests? I'm not familiar with perf test
harness.

thanks
Pan

+
 } // namespace WebCore