Running 3 ProgGuard optimization passes

base/android/base_proguard_config.flags

Index: base/android/base_proguard_config.flags
diff --git a/base/android/base_proguard_config.flags b/base/android/base_proguard_config.flags
index 904ee9842320f64e2f0affc48228f36a040dbfdd..94ae535ed69bfef228a1a79d54cba34dbd8cf7b2 100644
--- a/base/android/base_proguard_config.flags
+++ b/base/android/base_proguard_config.flags
@@ -50,6 +50,17 @@
   static *** isLoggable(...);
 }
 
+# The following chart was created on July 20, 2016, to decide on 3 optimization
+# passes.

[Yaron, 2016/07/20 17:10:05]

child process dirty memory, right? not browser. worth specifying

+# optimization passes | time | .dex size | dirty memory
+# -----------------------------------------------------
+#          1          | 0:48 |  5805676  |    488972
+#          2          | 1:07 |  5777376  |    487092
+#          3          | 1:24 |  5772192  |    486596
+#          4          | 1:42 |  5771124  |    486484
+#          5          | 1:56 |  5770504  |    486432
+-optimizationpasses 3
+
 # Class merging provides negligible .dex size reduction and method count
 # reduction (about 0.3% improvement on method count, and 0.1% savings on size),
 # and it messes up stack traces if the classes are optimized. Thus, it is in our