See the link to graphs below.
All graphs for this bug: https://chromeperf.appspot.com/group_report?bug_id=877199 (For debugging:) Original alerts at time of bug-filing: https://chromeperf.appspot.com/group_report?sid=f5b4b9e2968a1c929d112fadda7b02498b516f2c533b4cacedb17a430046926f Bot(s) for this bug's original alert(s): Android Nexus6 WebView Perf
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/160a029a640000
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/160a029a640000 Add PassiveDocumentWheelEventListeners to fieldtrial_testing_config by sahel@chromium.org https://chromium.googlesource.com/chromium/src/+/9187c7d059b7aa6342b39a19c7c32ba5aedd92cf 1.578e+07 → 1.713e+07 (+1.357e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
You can look at pinpoint analysis here: https://pinpoint-dot-chromeperf.appspot.com/results2/160a029a640000 The metrics suggest a regression in cc memory. The pinpoint also shows this. Here is the trace from a good [1] and bad run [2]. The trace has a memory dump as well. In the bad run cc has 6 tile_memory objects that are 3MiB each while in the good run it has 5 such objects. That leads to 3MiB difference. Any ideas why that is possible? Perhaps your patch allows the site to index (e.g., remove blocking event listener) which can lead to more tile being rasterized? [1] good: https://00e9e64bacc51aaed13b1c3704a15cfa52603c5b49df41c1aa-apidata.googleusercontent.com/download/storage/v1/b/chrome-telemetry-output/o/after_http_yandex_ru_touchsearch_text_science_2018-08-24_13-39-52_41042.html?qk=AD5uMEuwalocfJhAyGnYcJ_zhbjGjUYuQaOh9qKi-QxL1n9hds45zkFWqX-JKLHO-6nxqI7wxxhQSXQGCZvKUYt6IJf-EStBRoeRVxHPDIxTz3aF6GiiQez69r6G10rMUDFEtTi2u57vIte9SXxlAJiMZbn2O3SruhR2dkhVOhDSHfhiegQRNIE7ax3h7O-Y7ZdOyA8gAFlgt4yNn1ggwHqkRJnckxfQDTeRXZBGdIDDBdmofHYUr0Tk0A8bkWrxqBnnNn6UZnyKl2PoGFVxK0eVVKijVjTl6e7iK8U3oGrvg23S1cfnyZX6XgZ3t30Jdyi8OO4NP4N4s8MGt9ESwspVxn7kOFyJ4t2C0tYywh49MJtzQj-P86cbjFOYR0cKJu4rQrHJnm0zNvpXDT_wLv3QGO-vgoT6sQOT9iBJkDTgIf6lBVT4CVCWI1Ei1uutk7hzwqhUE84xFSFhzFWYLZ7TAV1TVWJWM95716RF7mbS7fc1DCoM_YIoMtnx63Kjz2TpJhrfoA_WB0KyFyCqZj4DjP-_zPc8TDPtyvg3kg6qlqzZoPTLlv0mY5PqHL1RWpUFuZ4bLOpzh06zt6QG4oYD7EdQl7OHI9TRwodT7loqPhZcGN7anL4ZXBxX_UHdaL-LqfsNg8zWxGJyc_nwT59xJgMvCn8ArlxTxs9VmR1b0uW5XmOD5bmpZKYA2j9sz0Ti22lCf7_r5Svnl49bM0nNoX1bBYC38dU2oGNIiln5BE178Pw2Y5hscYuOxxzZjkGcddIUUy0r6BLbzDpMphM5j4zgt-LoCiGkWg2BaPSp8n1GRLM3Dya29ekfosu7rFiO_XkVM07DFVs5A9L7Ze957hYUhTsv2yQLSlGMrBeRTn9Vklg-LI4 [2] bad: https://00e9e64bacaff769ca7e6588f39d68b4d1bde97bd5f655e073-apidata.googleusercontent.com/download/storage/v1/b/chrome-telemetry-output/o/after_http_yandex_ru_touchsearch_text_science_2018-08-24_10-05-51_34697.html?qk=AD5uMEsxlo45KllhqGxqyz-00brS3NebTzaadQSXmCGxZKTzhJuNp-MeLVvTm0Ta3fctGhhFVW9PWJfB0I7cV5g_iQqCIQvoJeQ4PLlLLMQwzpny_xfwQ_GmTw-n03bH2fKGxjKDpP8lUeTELtGtWAHC5GCQ2f-dKNLhKet99eHTq45BoCIy81sDkWPzOwS8-PkmKz_ECBEkZV8P5ofjxsSzGQgOIneHnzTcMDt8EkF7W1pGHh3MJnrb2qdIy6wHI8vQJ23IPgNR8m4sv5k4xELrf71saMv1b58cNk1OhKUvFkM9c4wc5s5dYZAoE5WCoB7kR9Z6OJ0ev6A9Ork3-FrFnMNQBCLIfZwru1Dmxl3SdAewPHiYi4dDYUs_eYpMjJ6atH8TEjdEqOVnvaD_Tyz7NslUj-CUvKTjHAYh3-fK9eksi-dQzVdwJ-VYTiy709aiztZ3DIvBFU7F0LCt578vSVN-_J4Kh9W8QkL_aW0GWM7PChpoPhYDX4c6mKZnYvF5QmlnIIEhPXiwHEcJjmyEhitffk4GyHdn7n-N6oMyS-7XQ_HBgVb8X2ldxhgnH3POQaU6ABB2kv4UtaDg92lzK1HaHGpWVbs6JBFkkhMStNwsX3yi2LrDxn7xbYP_lkLbXHTQ10Gw8IFZFyL8soo2b0IOjTuXJGU-Y2LZDFUNKCbQAXAGJIXFdY5I1zQWYKxyoYZxt8Zklo31uT7X_xryu85mYMDKiSmlxdY6vFcbZXhHRC81H02itMf1RXQ47nwLs4k29U9T7xaJAXEJJklRiEBuytiZSsATnsSvm-Wt-FnI7MedbaPgYmJUm83Qmgx3dMcaUGmqvOY__s3KS0AfQ0VVCADpswPk299HUgSDqznT8b7bf_A
Closing the bug since the graph shows that the regression has recovered.
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 23