[Experiment] purge-and-suspend

third_party/WebKit/Source/platform/text/CompressibleString.h

Index: third_party/WebKit/Source/platform/text/CompressibleString.h
diff --git a/third_party/WebKit/Source/platform/text/CompressibleString.h b/third_party/WebKit/Source/platform/text/CompressibleString.h
index 0ab99cf644b5376a25ab29af06e406fc2bbb752b..55b6820ee461383fda9f265c13fb2670d12f2232 100644
--- a/third_party/WebKit/Source/platform/text/CompressibleString.h
+++ b/third_party/WebKit/Source/platform/text/CompressibleString.h
@@ -22,7 +22,9 @@ public:
 
     CompressibleStringImpl()
         : m_string()
-        , m_isCompressed(false)
+        , m_originalLength(0)
+        , m_compressedData(nullptr)
+        , m_compressedDataSize(0)
     {
     }
 
@@ -31,7 +33,7 @@ public:
 
     bool isEmpty() const { return originalLength() == 0; }
 
-    bool isCompressed() const { return m_isCompressed; }
+    bool isCompressed() const { return m_compressedData; }
     unsigned originalLength() const { return m_string.length(); }
     bool is8Bit() const { return m_string.is8Bit(); }
 
@@ -70,7 +72,9 @@ public:
 
 private:
     String m_string;
-    bool m_isCompressed;
+    unsigned m_originalLength;
+    void* m_compressedData;
+    unsigned m_compressedDataSize;

[esprehn, 2016/08/05 23:00:58]

we should probably do this separately. I'm also concerned about the complexity
the current system causes because it assumes JS can run and force an uncompress.
What if we instead hide the compression the DOM?

[tasak, 2016/08/08 04:47:36]

Acknowledged.

 };
 
 class PLATFORM_EXPORT CompressibleString final {